Field Descriptions |
| |
| Feed Name |
This is the name of the feed as seen by event producers. |
| |
| Feed Description |
This is the description of the feed as seen by event producers. It should be as detailed as possible, but not exceed 2-3 paragraphs. |
| |
| Trigger |
This is the condition that activates the feed. Feeds can be triggered when ticket sales begin for an event or when a new user signs up for a producer's mailing list. |
| |
| Category |
Choosing a category will cause the Push Feed to trigger only for events in the category specified. If no category is chosen, the Push Feed will trigger for all events. Applies only to Push Feeds with the New Event Trigger. |
| |
| Post Each Date |
This option determines whether the Push Feed is triggered one time per event listing or whether it is triggered one time for each date on which an event takes place. Applies only to Push Feeds with the New Event Trigger. |
| |
| Login/Password Required |
When this option is enabled, it will require event producers to enter a login and password for the Target URL. This would typically be activated when a feed is created that allows event producers to automatically post events to their own account on a 3rd party site. |
| Send Login/Password as Auth |
When this option is enabled and Login/Password Required is enabled, it will send the user's login and password as an http Auth. The login and password may still be used in the Feed Body. |
| |
| Target URL |
This is the URL to which the POST Body is posted. |
| |
| POST Body |
This is the data that is sent to the Target URL when the feed is triggered. The POST Body may consist of XML data or HTML POST variables. The following variables may be used to obtain data about an event or mailing list member:
New Event Trigger
{e_name} - Event name
{e_venue} - Name of event venue
{e_address} - Event street address
{e_city} - Event city
{e_state} - Event state
{e_country} - Event country
{e_zip} - Event ZIP/Post Code
{e_phone} - Event contact number
{e_description} - Full event description
{e_short_description} - Brief event description (250 characters or less)
{date} - Event date
{min_price} - Minimum ticket price
{max_price} - Maximum ticket price
{url} - URL of event on Brown Paper Tickets
{login} - This is the login that the producer has set for this specific feed
{password} - This is the password that the producer has set for this specific feed
New Mailing List Member Trigger
{email} - Mailing list member's email address
{login} - This is the login that the producer has set for this specific feed
{password} - This is the password that the producer has set for this specific feed
Example: my_event_name={e_name}&my_event_date={date}&user={login}&pass={password}
In this example, the following four post variables would be sent via http to the URL specified in the Target URL field: my_event_name, my_event_date, user, and pass. These variables would contain the event's name and date, and the user's specified login and password. |
| |
| Affiliate ID |
This optional field name contain a Brown Paper Tickets Affiliate ID. If an Affiliate ID is supplied, the {url} variable will contain tracking data to associate the link with the given affiliate account. |
