Skip to content
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

Jump to bottom

Old campaign details added to returning visitor #11761

Open
lucasnetau opened this issue Jun 1, 2017 · 3 comments
Open

Old campaign details added to returning visitor #11761

lucasnetau opened this issue Jun 1, 2017 · 3 comments
Milestone
For Prioritization

Comments

@lucasnetau
Copy link

Campaign information is being added to visitors when they return, even months after a campaign has being completed. These visits may be through direct page loading or come via other referrers (with no campaign information) yet they are attributed to the campaign. This gives us incorrect information when checking the success of a campaign.

It appears that this campaign information is stored in the cookie _pk_ref and this cookie has a 6 month ttl.

Is this by design? Is there anyway that campaign information is only recorded for the visit where the campaign link is used as the entry point?
@hpvd
Copy link

hpvd commented Jun 12, 2017

Is there anyway that campaign information is only recorded for the visit where the campaign link is used as the entry point?

+1, yes this is indeed how it should work

@eramirezprotec
Copy link
Contributor

Is there anyway that campaign information is only recorded for the visit where the campaign link is used as the entry point?

+1

@BlinkHouse14
Copy link

+1
Any updates on this @tsteur ? We are also seeing old (and often "test") campaigns coming through long after their initial use via the _pk_ref cookie. In our case, we're noticing old campaigns coming through on Direct Entry visits.

Ideally, couldn't the campaign be cleared out or at least stored somewhere else for analysis of campaign success down the road?

Is there a current solution or workaround to this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
For Prioritization
Development

No branches or pull requests
5 participants
@hpvd @lucasnetau @eramirezprotec @BlinkHouse14 @innocraft-automation