You can also try to run _satellite.setDebug(true) in the developer console and observe any error the non-matching conditions stopped rules triggering.

There are two ways. One is using any condition in the Adobe Launch rule, any of them returning false will stop the rule from firing. Another one is setting s.abort in the Adobe Analytics extension custom code, which is what you are referring to. Actually, this one is setting to true (not false) to s...

Workspace is not designed for data export but for visual dashboards. To get data out of Adobe Analytics, you can refer to the official export guide, https://experienceleague.adobe.com/docs/analytics/export/home.html?lang=en, using Data Warehouse, Data Feed, and API.

One of the best parts of Adobe Launch is the extension, it is strongly suggested to use. For google ads, you can try gtag extension by Acronym, https://docs.acronym.com/analytics/adobe-launch/gtag. If no extension is insisted, you can use the custom code action to paste the google ads tag directly.

Moreover, adding 2 "Adobe Launch" scripts will only give you one single instance of _satellite where the JS loaded later won.

However, just a personal comment that the Activity Map function heavily depends on the HTML structure to identify what item had been clicked, https://experienceleague.adobe.com/docs/analytics/analyze/activity-map/link-tracking/activitymap-link-tracking-methodology.html?lang=en, or you may not get th...

As @Jennifer_Dungan mentioned, there is no "correct" or not for expiry for eVar. It all depends on your design. For my case, I usually have a custom event associated with each eVar, the most natural expiry for eVar is with that event. In the old days, this expiry is important for the attribution of ...

You can use the "Data Warehouse" function under the "Tools" menu and refer to https://experienceleague.adobe.com/docs/analytics/export/data-warehouse/data-warehouse.html?lang=en for documentation. You have to select dimensions and metrics for the export and this determine the final export file size....

Yes, that is a good thing to track with events. You will have two numeric events for coverageAmount1 and coverageAmount2, create calculated metrics and simply add them up. 

It somehow depends on how do you consume this data. For me, I started using EDDL with the "Adobe Client Data Layer" extension together with the WebSDK extension, so the structure of JSON being pushed into the adobeDataLayer is exactly the XDM and using the "Data Layer Computed State" from the "Adobe...