Task · Event settings
See which link a ticket was sold from
Keep the UTM parameters from the link somebody arrived on, and count your sales by link.
5 steps · About 3 minutes
-
Open the event's Settings, then Sharing
Your eventSettings -
Find Link tracking
Store query parameters from URLs is on for every event. The parameters on the link somebody arrived from are saved with the order they place.
go.tito.io/acme/summer-fetes-summer-fete/admin/settings/sharing -
Read Which parameters to keep
It starts at
utm_*, which keepsutm_source,utm_medium,utm_campaign,utm_termandutm_content. Separate names with commas. A*stands for any letters, soutm_*covers all five. -
Select Save
-
Open an order that came from one of your links
The parameters are on the order under Passed parameters.
Count the orders from each link
Open Reports and select Sales by link. It appears once an order has come from a tagged link, and it shows every sale grouped by utm_source.
To group by another parameter, like utm_campaign, pick it under Group by.
Each row is one value of the parameter, with its orders, tickets and gross. Not tagged counts the orders that came from an untagged link. Select a row for the ticket types each order bought.
Filter narrows to one value the same way, so you can group by Week and filter to utm_source newsletter to see how one link sold over time. Save the report to come back to it.
To count a partner's sales, give each partner a link with their own utm_source.
Export the orders from each link
Export your orders from Orders, under Actions. The export has a Link tracking group, with a column for each parameter your orders arrived with, like utm_source. An order that didn't come from a tagged link has those columns blank.
Ticket types says what each order bought. An order of one ticket type shows that type's name, and an order of several shows how many of each, like 2 × Standard, 1 × VIP.
The Export from Attendees has the same Link tracking group, with one row per ticket. Each row has the ticket's type and the parameters of the order it was bought on, so you can count a link's sales by ticket type.
Good to know
Tito can store the params that were passed, but it doesn't store long-life cookies, as some third-party analytics tools do.
- Turning the switch off stops parameters being saved. Clearing Which parameters to keep puts it back to
utm_*. - Ten parameters are kept per order. A name can be 40 characters long and a value 200.
- Ad click ids like
gclidandfbclidare kept if you add them by name. They identify one person where a campaign name identifies a campaign. - Anonymizing an order's buyer keeps its
utm_*parameters and removes the rest, including ad click ids and parameters you added yourself. See Data protection. - No matching parameters means nothing is stored.
- The account API serves them as
passed_parameterson an order, and a machine checkout can send its own. See Create an API key. - They stay with the order through checkout.
- Invitations and exhibitor portals keep them too, so the parameters on a campaign link to an invitation are saved with the order the invitee claims.
- Your widget keeps them too. The parameters on the page your widget sits in are saved with the order, so a campaign link to your own site works the same way as one to your event page. See Set up a widget.