Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPIKE] Mozilla Festival UTM Ticket Conversion Tracking #13512

Open
data-sync-user opened this issue Feb 17, 2025 · 6 comments
Open

[SPIKE] Mozilla Festival UTM Ticket Conversion Tracking #13512

data-sync-user opened this issue Feb 17, 2025 · 6 comments

Comments

@data-sync-user
Copy link
Collaborator

From https://mozilla-hub.atlassian.net/browse/MOFOTP-468

Request description

To be able to better understand the journey a user has taken to convert to a ticket sale, we want to be able to track the final UTMs associated with a user and pass these through to Tito so that we can accurately attribute sales channels in Salesforce.

The current Tito widget sends through the UTMs within the URL - this only works with the user converts on the page they land on. If the user browses to another page or leaves and comes back later we will lose the data of where they originated from.

To solve this we’re looking to store the last touch UTM of the user locally so it can be recalled a the time of the ticket ticket purchase.

More information on the current implementation of pre-filling UTM parameters into the Tito widget is available here:
https://ti.to/docs/api/widget#tito-widget-v2-prefill-data

Timeline

April 1st - Ticketing Launch

┆Issue is synchronized with this Jira Task

@data-sync-user data-sync-user changed the title Mozilla Festival UTM Ticket Conversion Tracking [SPIKE] Mozilla Festival UTM Ticket Conversion Tracking Feb 18, 2025
@data-sync-user
Copy link
Collaborator Author

➤ Ramon Ramos commented:

As mentioned on the meeting with the MozFest team, I propose using localStorage to capture UTMs on arrival, could persist that data between visits for accurate attribution. I’ll explore this approach further and share a implementation candidate for review.

@data-sync-user
Copy link
Collaborator Author

➤ Genevieve Baldassano commented:

Thanks Ramon Ramos ! Just checking in here, do you have a rough idea of when there will be some thing in place for us to review? Let’s make sure this is prioritized for the current/next sprint.

@data-sync-user
Copy link
Collaborator Author

➤ Ramon Ramos commented:

Genevieve Baldassano I worked on this over the weekend and im almost there, i have yet to inject the stored utms into the tito request but that should be covered today. I will post an update here at eod, if everything goes ok this could be done by Wednesday.

@data-sync-user
Copy link
Collaborator Author

➤ Genevieve Baldassano commented:

Ramon Ramos sounds good, thank you! Do you need any help on the SF side? cc: Mary Helen Ybarra Johnson Ali Latorre

@data-sync-user
Copy link
Collaborator Author

➤ Ramon Ramos commented:

The tito widget seems not to have any interface that allows for post rendering metadata injection for what I could read in the documentation and by reading the library itself. I started a support email thread with their team asking for an answer since this is a priority. I will post an update when I get a reply.

@data-sync-user
Copy link
Collaborator Author

➤ Marc Walsh commented:

Ramon Ramos I’ll invite you into our shared Slack channel with them, you might get a quicker answer there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant