There are 2 things that stood out to me in your "purchase" hit: purchaseID is "1e05e256-10ac-427c-8018-95d160f95a3d". That ID is 36 characters in length. But purchaseID can only accept up to 20 bytes, or 20 alphanumeric characters. (Ref: https://experienceleague.adobe.com/docs/analytics/implementati...

You need to provide the following to the code: bt.order.idbt.order.items Do you already have these as data elements?

I believe your procedure is correct. Although everything is built by Adobe, Schemas and Tags are really 2 different products in the Experience Platform. So while there is a relationship between your result XDM schema (created in Schemas) and data elements (created in Tags), there is no strong linkag...

Double-check for the Facebook pixel in your browser's Network console. When you load a page, search for network requests to "facebook.com/tr". Do you see any requests? You should see at least one that corresponds with the one shown in Facebook Pixel helper extension. Now click that network request t...

A Page View is tracked to Adobe Analytics when your web page runs the s.t() code. If you're using AEP Tags (a.k.a. Adobe Launch) as your tag manager, then you might be running a "Send Beacon" action of page view type from a rule, and that runs the s.t() code. This is also documented at https://exper...

@mattcheng1 wrote: Thanks for this insight! So you're saying that after putting the Launch script tag that's provided from Launch on my site/page, we can implement the s.t() and s.tl() methods on the page without needing to add a page or click tracking Rule in Launch? Yes -- provided you have made ...

You can try this: In a freeform table, include your eVar or prop that tracks your search term. Then add the Average Time on Site metric. Despite its "on Site" name, this metric really reports the average time based on the dimension in your table, i.e. your search terms. See https://experienceleague....

How is your Facebook pixel being fired for page views? Please describe the process, otherwise no one here will know how to help you.

In addition to @Jennifer_Dungan 's answer and going back to @aagk123 's question, you can track as many eVars/props/events as you want in a single tracking beacon call, and you'll still get charged for just that one beacon call, as @leocwlau has stated in his answer.

Yes, you can. In Launch, in the Analytics extension, there is a setting to make the "s" object globally available. Make sure that is selected. Then in your page code, you can use s.t() and s.tl() as you wish. You might want to include an if-else statement in your code to ensure that the "s" object i...