Hello! We are in the process of implementing the new EDGE network Adobe Web SDK and redoing our tagging. We've built some of the new server side tags with processing rules. Question for the forum: how can we QA events built in processing rules to make sure they are firing properly on the site? With client-side tagging, we would look at events using dev tools and/or Adobe Experience Cloud debugger, but now we cannot see them there anymore.
Open to suggestions!
Debugging is disabled by default, but can be toggled on in four different ways:
Please refer to : https://experienceleague.adobe.com/docs/experience-platform/edge/fundamentals/debugging.html?lang=en for more details.
Thank you for the reply! We know how to turn on the debugger. My question is how do we see events (custom events in Adobe like event 5 = lead submit) IN the debugger (or dev tools) when they are built using a processing rule?
Hey @meghanpowers - Thanks for the clarification, Have you tried enabling the Retrieve Post-Processed Hits option ? You should enable that if you want to see the values on Analytics hits after processing rules have run. You must be signed in to Adobe Experience Cloud for this feature to function.
When this option is enabled, a debugging parameter is added to your Analytics requests. Hits continue to be processed like any other hits. Platform Debugger polls the Analytics debugging API to retrieve post-processing rules values for any hits that have an original Hit ID. Post-processed hits have a purple background and are shown next to the original hit.
That's really interesting - thank you for the suggestion! Do you know where I go (in Adobe admin?) to enable that?
And do you know if it counts against our server calls or anything?
This feature was available in the old -- and now-deprecated -- Adobe debugger. The current Adobe Experience Platform Debugger does not have this feature, which is a huge loss precisely for this ability to inspect post-processed data.
Having said that, I don't know if the old debugger can show the post-processed data for data collected via Web SDK. I haven't tried it myself, but would be keen to know.
Processing Rules are an Adobe Analytics feature and have no relationship with Web SDK.
Think of Web SDK as a replacement for Analytics' own AppMeasurement, the code that collects Analytics-specific data to send to Analytics. But because Web SDK is not the native method for sending data to Analytics, so the Adobe debugger is not able to show the processed data after Processing Rules have been applied. You will have to rely on the final reports in Analytics to debug your data collection.
if we are going towards the processing rule "Use Adobe Analytics processing rules to set custom variables" mentioned in this URL https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-an...
To map the custom variables for Web SDK approach, then I have one question. Looks like for each report suite we have maximum of 150 rule we can create in processing rule then how come we accommodate all the custom variables (props 75, evars 250, 1000 events) in a single report suite????
You can try asking Client Care for an increase in the number of Processing Rules. You may have to pay for additional rules.