I believe it counts any pageview anywhere an mbox fires, regardless if there is an activity running or not.  For the 3rd party pixel, I would check with your account rep and have them monitor the pageviews and see if an additional mbox call will count against you.

I have never seen any reporting on how many page views an account has used in a given time period directly in Target.  They only way I have seen a report like this was by contacting my account rep.  Somehow they can look it up.  And really, the only time the number of page views we had used was ever...

Have you used the Preview Experience links before?  From the main list of activities, click on your activity.  On the overview tab, a little down the page on the left side will be a blue link that says "Preview Experiences".  Click on this and it will open a popup.  From the popup, add a url to the ...

I looked into this a little more and I think that you have set everything up correctly and that this is a bug.  I think it should be evaluating the audience on every page load, but for some reason once the user is put in the audience they get stuck there, even if the parameter isn't present.  I subm...

My bad here.  I overlooked that you said audience originally.  I think it may be that you are using an audience to check if the query parameter exists.  Once the parameter exists, the user is put into an audience.  I would think that the "current site page" would check every time to validate, but it...

Target shouldn't be caching things like that.  It should evaluate every time and make sure that the targeting is correct.  This is the first thing I would try to debug it.  Open a new Incognito window.  This should clear all cache and cookies.  Then go straight to XT 2.  Does XT 2 come up like you e...

Yes, it will reevaluate the requirements each time the pages loads.  Basically, it needs to check each time the page loads to make sure that the user still meets the requirements for the experience.  Can you give a use case or example on how you are planning on using it?With that said, there are way...

The old way in Target Classic was to wrap non global mboxes around specific divs on the page so that you could target content and changes to those divs.  This made it easy to run specific content tests to those specific divs on a page.  I find this to be limiting.  In Target Standard, you use global...

Your code looks fine.  So I would take a look at the data that is passed in your mbox.param('registrationdate') and validate that its always returning a date that you can use.  Since its a string, if there are any letters or other characters in there, it could be causing an error.  If the first char...

Can you post your full profile script code? Or if its long, at least the portion that the creates the date and converts the string to a number?  And also, in your value "2.0170713E7" there is a period and "E7".  Are these typos?  What is the E7?  I would think this is a string and not a number and t...