Hi @Joe_Y_1 , This sounds like a useful idea. In the meantime, really like @Brian_Johnson_ solution as a more automated method, but my team just uses a Core Constant variable to manually update and included with each library push. It's a bit tedious, but becomes ingrained in the workflow, and allows...

Hi @tomo_xxx , below is an image of the tracking done on this specific page. _satellite.bottom() working doesn't necessarily mean that AppMeasurement is running since _satillite is part of the tag manager (either DTM or Launch). In your DTM or Launch property you must have the Analytics tool/extensi...

True. Might be worth taking your solution to the next level and not only aborting AppMeasurement, but also putting malicious code on the page if the domain doesn't meet the criteria.... Simple solution would be to hide everything on the page.

Seems like a good solution, but doesn't hide the value of the tracking server. @Ishan_Sinha_ 's answer is the only one that completely masks all tracking activity from a client.

Piggy-backing off of @Andrey_Osadchuk 's answer, you could also set up your beacons to only fire on conditional events. In particular, create a condition within each rule that the domain meets the specific criteria. The only drawback would be that if someone were that highly motivated to commit frau...

Hi @Andrey_Osadchuk , it doesn't look like this is the same issue since you're using Adobe IDs, and this is probably just a bug, but there's similarly odd behavior using Federated IDs. My organization uses multiple IMS Orgs which means multiple instances of Admin Console. Since we use SSO there is s...

Do you mean data insertion API or reporting API?

Hi @ishank_tewari , It sounds like you may want to add/interact with some development logic on the page to make it clear when a page load corresponds to the actual transaction.As an example, there may be logic on the previous page which determines whether a transaction is successful and routes users...

Hi @omco77633670 , There are different versions of API you can use (v1.4 and v2.0) and depending on which you use, the requests look significantly different.If you are using v2.0, please review the request in swagger, here. Custom events use the same request, and you can run the /metrics API first t...

Thanks @MSchoenmakers-Signify . I appreciate you letting me know.