-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
How to track firebase dynamic link #4775
Comments
I found a few problems with this issue:
|
You can't track where the link was tapped from unless you create a custom link (or add custom parameters) for each source, but even then this will result in mismatches if a user ever copies a link and shares it to a different source. |
@morganchen12 You mean to say if I create a campaign, using FIRDynamicLinkGoogleAnalyticsParameters when one tap on Facebook I will pass Facebook in dynamic Link campaign. Then can track this link ? Also one confusion I have for getting campaign from first_open i.e installing from App Store and opening first time. Steps:
I got to know pending link via this code:
As this code will be written in open url block
@morganchen12 Please let me know does I am going in right direction? or something I need to correct or add here. |
You're headed in the right direction, but be aware that if a user copies your link from Facebook and shares it to a different website, the Facebook parameters will still be present and you will misattribute some percentage of your link opens. Also, when filing new issues please follow the issue template. |
i have added UTM parameter using FIRDynamicLinkGoogleAnalyticsParameters
Now i want to track the dynamic link like this,
if i have shared on Facebook, any one tap on that link then it will go to application if there else it will go to App Store.
After i need to show message based upon it’s source i.e welcome from Facebook like message.
So can we track dynamic link and check from where the link has been tapped and show relevant message based upon i’t source.
The text was updated successfully, but these errors were encountered: