• Resolved willywhy

    (@willywhy)


    I am trying to exclude logged in administrators, editors, etc. by creating an exception trigger according to your How To article. The GA tag still seems to fire even when logged in as admin and I can’t figure out why. Is it necessary to create a separate trigger as an exception or could the main DOM Ready trigger just include a condition of visitorType does not equal administrator?

    For the exclude trigger I am using visitorType ‘matching regex (ignore case)’ and ‘administrator|author|contributor|editor|web_designer|shop_manager’. And also Debug Mode ‘equals false’.

    Thank you.

    W

    • This topic was modified 7 years, 3 months ago by willywhy.
    • This topic was modified 7 years, 3 months ago by willywhy.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Thomas Geiger

    (@duracelltomi)

    Hi @willywhy,

    Thanks for your question!
    Yes, you can include the exclude condition in your positive trigger so that your GA tag does not gets fired once an admin is logged in.

    If you decide to use an exclude trigger, remember to use the same pageview event in the exclude trigger as in the positive trigger: so if you fire your GA tag on DOM Ready, use the DOM ready in the exclude trigger as well.

    Let me know if this works for you!

    Have a great day,
    Thomas Geiger

    Thread Starter willywhy

    (@willywhy)

    Hi Thomas,
    Your solution worked perfectly! I had a DOM Ready trigger with a Pageview exclude trigger.

    I suggest that you consider making this clear in your How To article on this topic. I created the tags and triggers exactly as described (see the photo you have in the final step of a DOM Ready trigger with Pageview exception that was created in previous step).

    Great plugin and support Thomas!

    WW

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Exclude logged in admin/editor’ is closed to new replies.