As far as I know, Griffon is a mobile solution only.

Automatic mappings (and schema locations) do exist for eVars[1-250], props[1-75], events[1-1000], and list[1-3]. _experience.analytics.customDimensions.eVars.eVar1 -_experience.analytics.customDimensions.eVars.eVar250 _experience.analytics.customDimensions.props.prop1 -_experience.analytics.customDi...

Yes, I've done this quite a few times for clients.  Using a product number (whether it is the SKU or some other unique product identifier) is always the best way to go.  Since you will be doing SAINT (classification) uploads anyway, here's the trick that will make your analysis of pre/post data much...

This seems like a really strange response.  Can you point me to some further official documentation on this approach? 

Ok,  So for a given website, the report suite would always be the same?  If that is the case, then you could create data elements that return the datastream identifier based on document.location.pathname.  You could have three datastreams, each configured for a given business site (with a different ...

At this point, I don't see any way to do this other than to use VISTA rules.  https://experienceleague.adobe.com/docs/analytics/technotes/vista.html?lang=en   Your use case seems valid.  I wish that there were a modern way to accomplish it.    -Stew        

Hmmm...  I thought that the unique orgId thing might be just a UI restriction but as you see below, it's enforced even when using the bare alloy.js library.  I'm not sure when this restriction came into being, but I'm certain that I tested the use of multiple instances under the same orgId at some ...

While you might be able to add this tag using a TMS, the real question is, "Can you add it quickly enough?"   I assume that you want to add this tag for SEO benefit.  If so, adding it with a tag manager, particularly an async implementation of Adobe Launch, is probably not going to get the tag into ...

Here's my code to create the JWT and get a bearer token.  You will probably need to change your metaScopes, but the rest should work as-is.    const auth = require("@adobe/jwt-auth"); async function getToken() { let buff = Buffer.from(process.env.ADOBE_IO_PRIVATE_KEY, 'base64'); let adobe_i...

I have experience with this.  Can you share the api call info that is yielding a 503?   Maybe I can help you out?  Also, if you are using nodeJS, I can share some code that I use for JWT creation and exchange.