Is there a mechanism to Encode and Decode URL params using AJO and WebSDK?

Hi ​@ap95,

Good use case, the encode/decode split is actually the right mental model here, you just need to handle each side independently.

Decode at WebSDK (client side), before sendEvent:

JavaScript’s native decodeURIComponent() is your tool. Parse and decode the URL param before it goes into the XDM payload:

const params = new URLSearchParams(window.location.search);

const rawId = params.get('identity');

const decodedId = decodeURIComponent(rawId);

alloy("sendEvent", {

  xdm: {

    identityMap: {

      EMAIL: [{ id: decodedId, authenticatedState: "authenticated" }]

    }

  }

});

Decode before sending, never pass the encoded value into the identity map or AEP won’t stitch correctly.

Encode at AJO (outbound side):

Use AJO’s encodeURL() helper function in your message/journey expression editor when constructing the URL param that will land on your site. This ensures what you encode in AJO is what decodeURIComponent() unwraps on the client.

Identity stitching:

For the event to stitch to the same profile, the decoded value must match the identity namespace and value already in AEP’s Identity Graph (e.g. ECID, Email, CRM ID). Use the correct namespace in identityMap, if the param carries an email, use EMAIL; if it’s a CRM ID, use your custom namespace. The namespace mismatch is the most common reason stitching fails silently.

If the param carries sensitive data (e.g. full email in the URL): consider hashing it server-side and matching against a hashed identity in AEP instead of passing raw PII in query strings.