Thanks, @Gokul_Agiwal , for tagging me. @sayyam_6772 and I had been messaging privately about this issue for a while. I understand and appreciate his concerns about how measuring Web Vitals with Custom Links would affect his bounce rate. One suggestion that I had provided was to store the measuremen...

Did you mean the Coefficient of Determination "R squared"? https://en.wikipedia.org/wiki/Coefficient_of_determination Instead of "Sum Rev Squared".

Yes, you still need Web SDK with Event Forwarding. Here's how the data flows: your website --> Web SDK --> Datastream --> Event Forwarding If you were to also use Web SDK to track your Analytics data, then the data would flow like this: your website --> Web SDK --> Datastream --> Event Forwarding ...

You generally cannot --  and should not -- run 2 Launch Tags properties in the same website. The main reason is that your property gets exposed in the "_satellite" object. Besides having such functions as "_satellite.getVar()", the _satellite object also encapsulates all of the code that makes your ...

Just to clarify: when you say "Launch Server Side", you're referring to Event Forwarding, right? https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en

"Unspecified" is reported in the absence of a value being tracked. https://experienceleague.adobe.com/docs/analytics/technotes/unspecified.html?lang=en#%E2%80%9Cunspecified%E2%80%9D-(or-%E2%80%9Cnone%E2%80%9D)-in-reporting  So if you don't want to see it, then you must ensure that a value is set (or...

Oh, I misread your question. I thought you had meant that you're getting "Unspecified" even when a value had been tracked to Tracking Code. Ok, then what you're experiencing is correct: when the "CID" parameter is absent, then indeed, you should expect "Unspecified" to be reported because there is n...

Wow, all of that code! I suggest that after this problem is resolved, you take some time to look at the extensions that are available in Tags to help you make full use of them instead. Otherwise, what's the point of using Tags, really? Your code looks correct. However, I noticed that you don't have ...

It could be that there is something that's blocking AA's AppMeasurement.js from being loaded properly in your page. Are you able to share the web page URL for us to preview and troubleshoot?

Assuming that you're using AEP Tags as your tag manager and are also using the Adobe Analytics extension there, then in the extension's configuration, under its Global Variables > Additional Settings section, ensure that the "Campaign" field has been set with "Query Parameter" and the value "CID". E...