search

firebase / firebase-ios-sdk

Firebase SDK for Apple App Development
https://firebase.google.com
Apache License 2.0
5.66k stars 1.49k forks source link

UTM parameters lost after relaunch #2910

Open b-onc opened 5 years ago

b-onc commented 5 years ago

[REQUIRED] Step 2: Describe your environment

[REQUIRED] Step 3: Describe the problem

We’re having a problem with utm parameters. We track those with AnalyticsEventCampaignDetails event whenever a link with with utm params are clicked (we're using branch.io for links) but we’ve seen that conversion events are not attributed to utm params. More specific, utm params are lost after a relaunch and future events are not attributed.

Facebook persists utm events and attributes future events with utm params. Firebase should also do the same, per spec (https://support.google.com/firebase/answer/6317518?hl=en) In the meantime, we've implemented our custom interim solution: save utm params to user defaults and report them on relaunch.

We’re searching for a way to test this functionality. Specifically, we want to make sure our utm parameters, once reported, gets attributed to future conversion events, so we don't need our custon solution. DebugView does not show utm params on events. How should we proceed?

Also asked the question under issue https://github.com/firebase/firebase-ios-sdk/issues/2462 and told to create a ticket for it. Asked the question on firebase slack but could not get a response.

google-oss-bot commented 5 years ago

I found a few problems with this issue:

b-onc commented 5 years ago

Hello? Any updates?

morganchen12 commented 5 years ago

@dmandar, is this intended behavior?

b-onc commented 5 years ago

Pinging for updates

b-onc commented 5 years ago

Hello @dmandar , did you have time to check?

b-onc commented 5 years ago

Monthly ping for updates

dmandar commented 5 years ago

To confirm, are you using dynamic links at all or is this a Firebase analytics question?

b-onc commented 5 years ago

@dmandar we are not using firebase dynamic links, we are using branch utm links and do the utm tracking with firebase. I guess this is an Analytics question.

paulb777 commented 5 years ago

Internally tracked at b/137757236

b-onc commented 5 years ago

Hello @paulb777 , is there any progress?

ggpuglia commented 5 years ago

Thank you for the feedback @b-onc. We are following up internally to discuss which is the best implementation for Analytics. I will reply back once I have an update.

In parallel, I would like to hear from you, your thoughts in the following points:

  1. What are the UTM parameters you are interested the most? Is "source", "medium", "campaign" (name) enough? Are "term" and "content" critical for your use case?
  2. You haven't mentioned gclid. Is this also relevant for your use case?
b-onc commented 5 years ago

Hello @ggpuglia

Thank you for looking into this.

  1. source, medium and campaign is enough for us, term and content is not important
  2. gclid is irrelevant for us

We're using https://ga-dev-tools.appspot.com/campaign-url-builder/ and only care for mandatory parameters

ggpuglia commented 5 years ago

Thank you for your input! We are tracking this as an internal project. Unfortunately, it might take us a little time to get this prioritized.

b-onc commented 5 years ago

Hello @ggpuglia , is there any progress on this?

b-onc commented 5 years ago

Hello @ggpuglia , is there any progress on this?

ggpuglia commented 5 years ago

Sorry, the development team hasn't had a change to prioritize this. We are working on getting release soon.

mrfelton commented 3 years ago

Have there been any updates on this in the last year?

tongdatarunsdeep commented 3 years ago

Hi, has there been any update on this?

We have run into a similar issue, with AnalyticsEventCampaignDetails not firing events as expected, but when manually setting campaign, source, and medium parameters on other events, they will get attributed in the acquisition report.