Agreed. It's not exactly clear where that specific step occurs, but it's definitely in the "After Processing Rules" section, which means it happens after anything we can configure either through data collection or Processing Rules.

@Jennifer_Dungan is correct. Dynamic variables will populate with what's visible in the network call. This means that using D=pageName to populate an eVar will copy up to 255 characters into the eVar. It will not truncate to 100 characters.   For reference, here are more details on order of operatio...

@AAanon - No problem.I would suggest a single direct call rule to handle all of your video tracking. For this sake of this post, let's assume this rule is named "dcr:video progress" and that we're doing the following two things:Setting Adobe Analytics variablesSending the Analytics beacon with a lin...

@AAanon - It's actually pretty similar. Using the documentation on the Wistia site, there's a quick reference to interacting with videos that are embedded via IFRAME. Assuming you have the necessary Wistia JS library on the page (//fast.wistia.net/assets/external/E-v1.js), you should be able to use ...

@helenr35573098 - Based on what your image shows, I'd guess you have either a bot that's hitting your site, or internal processes that hit the site at somewhat high volume. My suggestion would be to segment for hits that match that OS Type and dig further to see if you can figure out where the traff...

@Trystan_Colwyn- - Using the first fetch() example here:fetch('./api/some.json') .then( function(response) { if (response.status !== 200) { console.log('Looks like there was a problem. Status Code: ' + response.status); return; } // Examine the text...

@Trystan_Colwyn- - If your API/request has a callback/response, I would suggest one of the following:Push the information to your data layer (assuming you're using an event-driven data layer)Use a direct call rule (DCR) that can be triggered directly in your callbackIn your callback, trigger a custo...

You make it an "exclude" segment by selecting the option highlighted below. (This is the only difference between your two segments.): Once selected, the definition will display the following. Note that it now says "exclude" and the left border is red:  

I would probably set up the following segments: Segment 1: INCLUDE Visits where page = "homepage"Segment 2: EXCLUDE Visits where page = "homepage" The exclude segment is important. If you say "include where page does not equal 'homepage'" and the visit includes views of "homepage" and "anotherpage",...

 Bounces: https://experienceleague.adobe.com/docs/analytics/components/metrics/bounces.html?lang=en Exits: https://experienceleague.adobe.com/docs/analytics/components/metrics/exits.html?lang=en Entries: https://experienceleague.adobe.com/docs/analytics/components/metrics/entries.html?lang=en