Skip to main content

Snowflake Embedded Identity Release Notes

Release 1.1.0

Release date 8/1/25

This release introduces two new major features:

Expanded Deconfliction Support

CID mapping jobs can now be run in Household Expansion or Event Integrity modes in addition to Standard and Maximized 1P Fidelity. Household Expansion augments the deconflicted mapping by pulling in additional RampIDs from the households present in the input data. Event Integrity attempts to retain all customer CIDs with as few conflicts as possible. For more information, see “Using Deconfliction on a Universe Dataset”.

Global Support

A new global native app listing has been released allowing for PII, Email, and Transcoding workflows to be run without a backing Identity graph. These workflows produce derived RampIDs exclusively.

Additionally, the US native app now supports a new derived-only mode that emulates this behavior which can be used for creating derived RampIDs appropriate for PAIR for example.

Updates
  • Deconfliction now supports “Household_Expansion” and “Event_Integrity” modes

  • Customers can now run the derived only flow for PII and email resolution. For running the derived only flow, the derivedOnly parameter should be set to true in the config interface and countryCode should be passed when running from outside of United States. Country code is not required for email workflows.

  • Various other quality of life improvements added and minor bugfixes  performed as part of this release

Breaking Changes
  • No breaking changes were made in this release

Backward Compatibility
  • Release fully compatible with the previous versions

  • No action required for existing implementations

Additional Resources

Release 1.0.0 Patch 2

Release date 6/3/25

This is a patch release adding background improvements and updating the RampID counts reported by different workflows to be more consistent.

Updates
  • Derived and Maintained RampID counts are now reported for all workflows. These counts were previously reported for CID mapping, PII, and email workflows. MAID, CTV ID, and cookie workflows now report the counts as well.

Breaking Changes
  • N/A

Backward Compatibility
  • No action required for existing implementations

Additional Resources

Release 1.0.0 Patch 1

Release date 4/8/25

This is a bugfix release fixing an issue with large PII jobs.

Updates
  • A bugfix was released which allows large PII jobs with no email or phone mapped in to be run successfully. Previously these could fail if the Native App determined that it needed to batch the input into multiple batches because email or phone prospecting would be run without the required touchpoint columns existing.

Breaking Changes
  • N/A

Backward Compatibility
  • Release fully compatible with the previous Beta version

  • No action required for existing implementations

Additional Resources

Release 1.0.0

Release date: 3/31/25

This release introduces LiveRamp's Embedded Identity Resolution product in Snowflake into General Availability (GA).

Major Updates

This GA release supports Identity Resolution, which allows you to resolve an identifier (a device ID or PII, such as name, address, email, or phone) to LiveRamp's person-based, pseudonymous identifier, RampID, as well as RampID Translation, which translates a RampID in one domain to a RampID in another domain.

Additional changes:

  • We've updated the interface to allow for the metadata table to include a single variant, streamlining the configuration and providing additional flexibility.

    • The deconflictionConfig parameter is now also supported at the top level of the config interface.

    • The limit parameter is now also supported at the top level of the config interface.

  • Validation on table names now checks that they have fewer than 256 characters

  • Validation check added for read permissions on metadata table

  • Multiple job types are now able to share the same input table for CID mapping

  • The lr_resolution_and_transcoding call now fails if there is an error in the billing integration and no (deprecated) metrics table was provided

  • Various error message improvements

Backward Compatibility
  • The release is fully compatible with the previous beta version.

  • No action is required for existing implementations.

  • Note that the new config interface no longer supports passing logging and metrics tables.

Additional Resources