This message was deleted.

You can track 1. landing page visit and using utms trace it back to a campaign, keyword, ad etc 2. button click 3. app.requestly.io visit I don't it is possible to track 1. Chrome store page view 2. Installs extension

Yes, this is what I'm also thinking of. But don't you think those data won't give us the actual conversions of the ads? @Ashwin Sande

what is actual conversions for you?

extension installed, and eventually account activated.

@Kaavian these methods will not give you actual conversion attribution. I think a better way would be to use a 3rd party click tracker, which will give you IP data which you can then check against your user db to see which IPs match.

@Aniruddh Jain thanks for the tip. Helps a lot 🙏

I dont think there is a way to track "extension installed" in any way. But for "account activated" on app.requestly.io can be tracked via cookie only. @Aniruddh Jain: Does Chrome share IP addresses? If the answer is no, then what @Kaavian wants can be tracked using web analytics tools-> 1. landing page visit and using utms trace it back to a campaign, keyword, ad etc 2. button click on "install...." on the landing page 3. app.requestly.io account activated I just think it is much easy that way because IP way is tough and difficult to separate 2 users from same IP. e.g., 2 users working from same company or 2 users working from same coffee house might have the same IP. Whereas cookies can set separate

there is a problem here, we don't collect any user data like email or name initially. We let the users to use the product and then after a while only we ask for sign up details. So How do we backtrack the account activated to the campaign?

Cookie based approach. If you are available for a call- I can show you how we do it. DM me

@Ashwin Sande browser is irrelevant in this case. any server request to requestly servers will be accompanied by an IP address from where that request originated. also doesn't matter if there are 2 or 10 users from the same org, we'll do the attribution at an account level, so any one we're able to catch is fine. coffee shop use case might be different but i believe it is more like an edge case. again we're talking about what's doable in the realm of these circumstances.

I am not denying that IP address solution is possible. All I am saying cookie based solution is an option as well and can be implemented easily using GA or web analytics tools rather than IP matching solution which will require data engg efforts.