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

New_Visit=1 parameter in connection with Content-tracking / events (2.12.0) #7557

Open
peterbo opened this issue Mar 27, 2015 · 1 comment
Open

New_Visit=1 parameter in connection with Content-tracking / events (2.12.0) #7557

peterbo opened this issue Mar 27, 2015 · 1 comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
Backlog (Help wan...

Comments

@peterbo
Copy link
Contributor

peterbo commented Mar 27, 2015

When the parameter new_visit=1 is appended, and content / event tracking is in use, a new visit is created for every single request (goal / event / content impression) resulting in a lot of new visits with 0 actions (since these are not counted as action).

The expected behavior would be if the new_visit=1 parameter would only account for the main tracking request (or request counted as "action") and not for "sub"-requests like event / goal / content requests.

This is open for discussion since I'm not 100% sure, what to expect from this behavior and what the overall use cases are.
@mattab
Copy link
Member

mattab commented Apr 8, 2015

Hi @peterbo

Thanks for the suggestion.

a Workaround may be to append new_visit=0 after tracking the pageView and right before the Contents pieces are tracked with trackAllContentImpressions or via trackVisibleContentImpressions

This is open for discussion since I'm not 100% sure, what to expect from this behavior and what the overall use cases are.

+1

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Apr 8, 2015
@mattab mattab added this to the Mid term milestone Apr 8, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
2 participants
@mattab @peterbo