Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Email Address tracked on not

Avatar

Level 5

Hi All,

We have been informed that there are forms out there, where the mail address is tracked,
before the form has even been submitted. Apparently ABC.com (not ABC.de) is affected by this issue.

Now the business is wondering if we have a similar issue on ABC.de

I doubt that this is the case.
How to cross check that mail is tracked or not, if any data is collected before a form has been submitted on ABC.de

Please guide. Thank you

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Assuming you don't have any documentation for the tracking implementation (which should outline what is and isn't being tracked and where), you would still need to test the scenarios manually to find out.

 

Using a tool (browser extension) like the Experience Cloud Debugger or Experience Platform Debugger, you will need to manually go through all the flows (possibly in a QA or UAT environment, or maybe even on Prod if you are concerned about inconsistencies between environments).

 

If you are testing on a browser that doesn't have the extension available, then you can look at the Network panel in the developer console (filter for "b/ss") and look at the actual server call, you may need to copy it out to something where you can break it out to read it easier. Parameters like c2 are props (c being custom prop, 2 being your prop number), v5 are eVars (again the # corresponds to the eVar number), g is the backend URL, ch is your site section, etc). It's not as easy to test this way, but is doable.

 

Then you will have to read through all the collected data and see if emails are being collected and where.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Assuming you don't have any documentation for the tracking implementation (which should outline what is and isn't being tracked and where), you would still need to test the scenarios manually to find out.

 

Using a tool (browser extension) like the Experience Cloud Debugger or Experience Platform Debugger, you will need to manually go through all the flows (possibly in a QA or UAT environment, or maybe even on Prod if you are concerned about inconsistencies between environments).

 

If you are testing on a browser that doesn't have the extension available, then you can look at the Network panel in the developer console (filter for "b/ss") and look at the actual server call, you may need to copy it out to something where you can break it out to read it easier. Parameters like c2 are props (c being custom prop, 2 being your prop number), v5 are eVars (again the # corresponds to the eVar number), g is the backend URL, ch is your site section, etc). It's not as easy to test this way, but is doable.

 

Then you will have to read through all the collected data and see if emails are being collected and where.