Skip to main content
Solved

Reconcile users on our landing page with users in our web app

H
Conversationalist
Forum|alt.badge.img

Hey Everyone

Is there a way I can track users that visit our landing page and merge them with the tracking of users on our web app (on a subdomain)?

Our landing page is on Webflow. When users sign up, they will go through an auth0 sign up page before getting redirected to our web app (on a subdomain url). 

I already have Amplitude working on webflow through the javascript sdk (so I can track visitors and UTM sources), and I also have working on our web app using backend server tracking through HTTP requests (to track actions on our product), but I can’t reconcile the two, and they seem to be getting created as separate IDs.

 

I’ve tried following https://help.amplitude.com/hc/en-us/articles/115003135607#h_f717e48c-460c-4a17-abd7-102327673798 to set up cross domain tracking, but we can’t pass the device ID from webflow to our web app, because a user needs to sign up on a third party auth0 page in between.

Are device IDs suppose to be automatically reconciled, or are we missing a setup (e.g. do we need javascript sdk on our web app too)?

 

Thanks!

Best answer by Denis Holmes

Hi @hypotato ,

 

Thanks for writing into Amplitude Community!

 

Do you own the subdomain? In this case, it would be following the cross-domain tracking article that you linked. Device IDs can be merged together as described n the article. If you have a matching Device ID for the user between the web flow and the back end, they should be able to merge on that unless there are several users using the same Device ID, which could make it tricky. You would need to be able to pass the Device ID between the two flows. Do you think you can reach out to the provider of the 

third party auth0 page and see if they can pass the Device IDs for you? This would unfortunately be the only way we would have and we have no methods for getting around third party auth0 pages unless you reach out to them and see if they would allow you to pass the Device ID as some other customers have done this. 

 

I hope this helps! Let me know if you have any other questions that I can help you!

 

Kind Regards,
Denis

View original
Did this topic help you find an answer to your question?

9 replies

Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Denis Holmes
  • Team Member
  • 448 replies
  • Answer
  • March 22, 2022

Hi @hypotato ,

 

Thanks for writing into Amplitude Community!

 

Do you own the subdomain? In this case, it would be following the cross-domain tracking article that you linked. Device IDs can be merged together as described n the article. If you have a matching Device ID for the user between the web flow and the back end, they should be able to merge on that unless there are several users using the same Device ID, which could make it tricky. You would need to be able to pass the Device ID between the two flows. Do you think you can reach out to the provider of the 

third party auth0 page and see if they can pass the Device IDs for you? This would unfortunately be the only way we would have and we have no methods for getting around third party auth0 pages unless you reach out to them and see if they would allow you to pass the Device ID as some other customers have done this. 

 

I hope this helps! Let me know if you have any other questions that I can help you!

 

Kind Regards,
Denis

Saish Redkar
1 person likes this
  • Saish Redkar
    Saish Redkar
H
Conversationalist
Forum|alt.badge.img
  • hypotato
  • Author
  • Conversationalist
  • 5 replies
  • March 22, 2022

Thanks @Denis Holmes. Yep, we own the subdomain as well. 

If we own the domain that our webflow landing page is on and have amplitude there, and we own our subdomain that our web app is on as well, and also have amplitude there, will Amplitude produce the same device ID for both our landing page and our web app and automatically merge them together? 

Or do we have to explicitly pass the device id between the sites as you mentioned? (e.g. if our landing page is mydomain.com, and our web app is on app.mydomain.com)

Thanks!

Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Denis Holmes
  • Team Member
  • 448 replies
  • March 23, 2022

Hi @hypotato ,

 

Thanks for the reply! You would need to explicitly pass the Device ID between the sites and then when it is passed and assigned to the new user, Amplitude will know “Ah, this new user is the same as this other user on the landing page” and then merge them together :)

 

I hope that helps! :D 

H
Conversationalist
Forum|alt.badge.img
  • hypotato
  • Author
  • Conversationalist
  • 5 replies
  • March 23, 2022

Thanks @Denis Holmes ! 


Possibly a separate question, but I’m having difficulty retrieving the Device ID on my Webflow page. I’ve tried using amplitude.getInstance().options.deviceId; but it returns with this error:

Cannot read properties of undefined (reading 'deviceId')

I’ve also tried Amplitude.getInstance().getDeviceId() but it says that getDeviceId is not a function. These are being adding this to the Head HTML code right after amplitude.getInstance().init() on my webflow site.

Is the Device ID not being set or could I be accessing it incorrectly? I’ve tried adding this as a callback function as part of .init() or .getInstance().onInit() as well but both of those still return the same errors.

 

Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Denis Holmes
  • Team Member
  • 448 replies
  • March 23, 2022

Hey @hypotato ,

 

I think this is the order of things. If you want to set your own Device ID, I would do that first. Otherwise, I would log an event first and then get the Device ID. Such as ;

var text = amplitude.getInstance().options.deviceId;

Can you see if that helps? Thank you!
 

 

H
Conversationalist
Forum|alt.badge.img
  • hypotato
  • Author
  • Conversationalist
  • 5 replies
  • March 24, 2022

Edit: ignore this, but leaving the question here in case it’s useful for anyone in the future. I made a mistake by calling amplitude.getInstance() inside the callback function for init(), when instead the instance is actually passed an argument. So getting the device id is actually just instance.options.deviceId; Thanks Denis!

 

Hi @Denis Holmes , 

Even after logging an event, it still shows this:

[Amplitude] TypeError: Cannot read properties of undefined (reading 'deviceId')

This is what I have in my HTML <head> code in webflow:

amplitude.getInstance().init("<MY_API_KEY>", null, {
    saveEvents: true,
    includeGclid: true,
    includeUtm: true,
    includeReferrer: true
  }, function() {
    var eventProperties = {
     'page_type': ‘landing_page’
    };
    amplitude.getInstance().logEvent('page visit', eventProperties);
    var device_id = amplitude.getInstance().options.deviceId;
    console.log(device_id); 
  });

 

I’m already only calling amplitude.getInstance().options.deviceId; in the callback function after initialization, and I’ve also added a logEvent() before that, but it still says that deviceId is undefined. Could I still be missing a step, or perhaps my order might still be incorrect?

Denis Holmes
1 person likes this
  • Denis Holmes
    Denis Holmes
Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Denis Holmes
  • Team Member
  • 448 replies
  • March 27, 2022

Hi @hypotato !

 

Apologies, I was out sick for a few days. It looks like you were able to get this to work! Can you confirm for me? Thank you!

H
Conversationalist
Forum|alt.badge.img
  • hypotato
  • Author
  • Conversationalist
  • 5 replies
  • March 29, 2022

Hey @Denis Holmes , all good—it works nicely! Thanks for your help and hope you’re better :)

Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Denis Holmes
  • Team Member
  • 448 replies
  • March 29, 2022

Sounds good @hypotato ! :) Thank you for your kind words :D If you have any other issues, feel free to post again at any time, happy to help! 

Reply


Helpful Members this Week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings