Fields with Special Behaviors

🚧
Warning
In the latest version of Woopra, some of these fields, for instance campaign fields, have changed the way they work in the Woopra Interface.

There are a number of visitor, visit, and event property keys that, if sent as part of the tracking request, will cause some special behavior in the Woopra UI. For instance, sending campaign_name as an event property will actually allow it to be picked up by the system for campaign reporting, and will also show the event's campaign in the interface differently from the rest of the event properties.

Here is a list of fields that have some special behavior by convention:

Field Name	Property Scope	Special Behavior	Discussion
`url`	Event Property	Parsed for pageview data, campaign data, etc.	Woopra will read `utm_` and `woo_` tags, and include them as campaign data for the event.
`campaign_name`	Event Property	Treated as campaign attribution data	Woopra displays campaign data specially in each event that has it so as to make attribution clearer. Also, this data when sent with any event, will be used to generate the new Attribution Reports.
`campaign_id`	Event Property	Treated as campaign attribution data
`campaign_source`	Event Property	Treated as campaign attribution data
`campaign_medium`	Event Property	Treated as campaign attribution data
`campaign_content`	Event Property	Treated as campaign attribution data
`campaign_term`	Event Property	Treated as campaign attribution data

🚧Warning

🚧
Warning