Losing sales from in-app browsers on mobile?

D Fish

Registered Member
Joined
May 2, 2020
Messages
78
Reaction score
16
Hi all,

It occurs to me that cookies aren't shared between browsers, and many traffic sources on mobile use their own in-app browser. Basically every social media app has its own in-app browser (even the gmail app has an in-app browser on android).

Is there any way to overcome the fact that many (if not most) people probably have their payment information autosaved on only their primary browser that they normally use to make purchases?

If they click your link in, let's say, in the Instagram app (within the in-app browser) and it they get to the checkout page, at this point many people will copy that link and paste it into the browser that has their payment info autosaved, so they don't have to manually enter it (or, they just open their preferred browser, and use google to navigate back to the sales page.

In both cases, they probably lose your affiliate tag on their url. I wonder how many sales affiliates lose to this. Is there any possible solution?
 
Last edited:
Hi all,

It occurs to me that cookies aren't shared between browsers, and many traffic sources on mobile use their own in-app browser. Basically every social media app has its own in-app browser (even the gmail app has an in-app browser on android).

Is there any way to overcome the fact that many (if not most) people probably have their payment information autosaved on only their primary browser that they normally use to make purchases?

If they click your link in, let's say, in the Instagram app (within the in-app browser) and it they get to the checkout page, at this point many people will copy that link and paste it into the browser that has their payment info autosaved, so they don't have to manually enter it (or, they just open their preferred browser, and use google to navigate back to the sales page.

In both cases, they probably lose your affiliate tag on their url. I wonder how many sales affiliates lose to this. Is there any possible solution?

Did you eventually find a solution to this?
 
There is no solution to this. In-app browsers have their own sessions, they don't share sessions with the browser.
Good old times with flash cookie would solve the issue, but ye - the only solution is to disable placements in-app (talking about GAds).
 
There is no solution to this. In-app browsers have their own sessions, they don't share sessions with the browser.
Good old times with flash cookie would solve the issue, but ye - the only solution is to disable placements in-app (talking about GAds).
Do you mind explaining this in yellow? I have no clue what it means
 
Back
Top