wilem121982013

[scarlet peak]

Hi 👋 sorry, I won't have much insight into why the tracking solution you're using isn't working well with our URLs, especially as I don't have context on what you mean when you say it stops working.

Have you been able to determine if there is something specific about our URLs that's causing your tracking solution to have problems?

[frosty lava]

i have a navigation provider, which contains a page tracking event from rudderstack, on the page. load it triggers the event but when i make a paymentIntent and it succeed and redirect to the page i pass in the return_url the event is not trigger anymore

window.rudderanalytics.page("", { ...user, path, section_name: "check" });

here the event, which is a useEffect that check when the location change

[scarlet peak]

Yeah, sorry, that's not something I know anything about. Does the page you're using for your return_url have the necessary components on it to trigger your tracking (really not sure how rudder works here, mostly guessing at possible causes)

[frosty lava]

yes, its actully a script in the index.html and yes it has the component to trigger since its in a provider that englobe all my app

[scarlet peak]

Hm, gotcha. In that case, would it be problematic if the redirect flow takes you to an intermediary page that you don't control? I'm not sure what payment method type you're testing with currently, but some of them require hitting a third-party page (like a bank authentication screen) in the middle of the flow. That's likely not a concern if you're primarily testing with cards right now though.

[frosty lava]

i use the confirmSetup , to make a paymentIntent we have like a banking pop up that appear to validate the payment but not in my case right im just testing with cards right now