← Back to Physical Marketing Intelligence Center

Indemption Integrations

Engage existing Salesforce records. Generate new leads.

Connect physical and digital engagement to Salesforce with personalized dynamic QR codes for known contacts and shared QR experiences that identify and generate new leads. Every interaction can open a Pit Stop, capture intent, enhance customer data, and route approved updates back to Salesforce.

Indemption preserves the originating Salesforce record, project, QR code, and Pit Stop context so engagement does not become disconnected from the CRM.

Indemption is a customer engagement & attribution platform—an engagement layer on top of Salesforce, not simply another Salesforce connector.

Sign up free and receive 100 free credits to build your first campaign and connect Salesforce.

Salesforce manages customer records. Indemption captures engagement.

Salesforce remains the CRM and system of record. Indemption is the engagement layer that connects scans, responses, physical marketing, and customer actions back to the appropriate Salesforce Contact or Lead.

Salesforce stays the system of record. Indemption captures the journey that happens outside the CRM.

Existing Contacts and Leads

Import Salesforce records, preserve the object type and record ID, and give each known record a unique, measurable path into a personalized Pit Stop experience.

New Lead Generation

Turn a shared QR code into a measurable path that identifies the visitor, matches an existing Salesforce record when possible, or creates a new Lead or Contact only when configured.

Engagement can come from print, packaging, signage, events, retail displays, brochures, flyers, digital content, and other QR-enabled touchpoints—then connect back to Salesforce through:

  • Unique dynamic QR codes for known records
  • Generic QR codes for new lead generation
  • Pit Stop landing experiences
  • Lead forms
  • Offers
  • Wallet pass creation Being introduced
  • USPS delivery activity
  • Contact and lead enhancement
  • Approved data write-back
  • Campaign, project, Pit Stop, and QR source context

Two QR paths. One connected Salesforce journey.

Indemption supports two distinct QR models—one for known Salesforce Contacts or Leads, and one for shared lead generation. Both can open a Pit Stop and keep the originating Salesforce identity and source context connected.

Engage Known Salesforce Records

Import Contacts into an Indemption project, preserve the Salesforce Contact ID, and give every known record a unique measurable path into a personalized experience.

When records are imported or connected from Salesforce, Indemption can retain the originating Salesforce object and record ID and associate a unique QR experience with that person. When they scan, Indemption can recognize the originating record—subject to the configured experience and available identity.

  • Import Contacts and preserve the Salesforce Contact ID
  • Unique dynamic QR tied to a known Contact or Lead
  • Recognize the originating record when they engage
  • Personalize the Pit Stop experience
  • Collect engagement or enhanced information
  • Write approved updates or activity back when configured
  • Preserve campaign, project, and QR source context
  1. Salesforce Contact or Lead
  2. Unique Dynamic QR Code
  3. Personalized Pit Stop
  4. Customer Interaction
  5. Existing Salesforce Record Updated
  6. Activity and Source Preserved

Generate New Leads

Publish a generic QR code, collect identifying information through a Pit Stop, and match or create the right Salesforce record according to your configured workflow.

A generic QR code is not initially tied to one specific person. It can be placed on signs, brochures, packaging, advertisements, event materials, retail displays, flyers, shared mail pieces, or other public marketing materials.

When an unknown visitor scans, the Pit Stop captures intent. After the visitor identifies themselves, Indemption can search for an appropriate Salesforce match, update an existing record when a reliable match exists, or create a new Lead or Contact only according to the configured Salesforce workflow.

  • One generic QR used by many people
  • Capture identity and intent through a Pit Stop
  • Search Salesforce for a matching Contact or Lead
  • Update a reliable match when found
  • Create a new Lead or Contact only when configured
  • Preserve campaign, QR, project, and Pit Stop source
  1. Generic QR Code
  2. Anonymous Scan
  3. Lead, Offer, or Wallet Pit Stop
  4. Visitor Identifies Themselves
  5. Match or Create Salesforce Record
  6. Activity and Source Preserved
A scan alone should not create a duplicate Lead or Contact. Identity matching and record creation happen through the Pit Stop experience and your configured Salesforce workflow—not from every anonymous scan.

Complete engagement context

Knowing which campaign generated a response is only part of the story. Indemption keeps who engaged and what caused the engagement connected to the right Salesforce record.

Personalized QR codes identify known Salesforce records, while generic QR codes preserve the source that generated a new lead. An anonymous generic scan does not automatically identify a person. Identity is established after the visitor provides information or completes another configured identification step.

Indemption can preserve:

  • Salesforce object type (Contact or Lead)
  • Salesforce record ID
  • Source contact or lead
  • QR code
  • Pit Stop
  • Campaign
  • Segment
  • Project
  • Mailing job
  • Physical or digital source
  • Lead form
  • Offer
  • Wallet pass creation
  • USPS activity
  • Resulting CRM update

Physical engagement sources

  • Printed QR codes
  • Direct mail
  • Retail displays
  • Product packaging
  • Event signage
  • Brochures and flyers
  • Business cards and sales sheets

Digital & connected sources

  • Mobile wallet pass creation
  • Lead forms
  • Offers
  • Landing-page Pit Stops
  • USPS delivery milestones
  • Future POS integrations
  • Future connected applications

Pit Stops: the experience between the scan and Salesforce

A QR code starts the interaction. A Pit Stop determines what happens next.

Pit Stops are the experience and decision layer between the QR scan and Salesforce. They capture intent, personalize the next step, and help find, enhance, or create the right CRM record while retaining source and project context.

QR Scan Pit Stop Recognize or Identify Engage Update Salesforce Preserve Source Context

What a Pit Stop can do

  • Recognize a known Salesforce record from a personalized dynamic QR
  • Collect information from a visitor
  • Display personalized content
  • Capture a lead form
  • Present an offer
  • Create a wallet pass when that experience is enabled
  • Route the interaction through selected feeds or native applications
  • Retain the source and project context

What each Pit Stop can do in Salesforce

  • Find, enhance, or create a Contact or Lead according to configuration
  • Preserve the originating Salesforce object and record ID
  • Record engagement and source context when configured
  • Route activity through provider-agnostic feeds and native-app connections
  • Keep the originating QR, Pit Stop, campaign, and project connected

Enhance Salesforce records—then write back with control

Indemption does not just move fields. It can improve data quality and carry Salesforce-specific context through the project—then write approved enhancements back to selected Salesforce fields after review and mapping.

How Salesforce fields are preserved

  • Standardized Indemption fields remain intact
  • Salesforce-specific unmapped fields are preserved
  • Additional source fields can be carried through the project
  • Staged CSV files expose those additional fields as usable columns
  • Users control mappings and write-back behavior

Enhancement examples

Improve CRM usefulness when enrichment services are enabled.

  • Corrected mailing address
  • Address 2 or mapped custom address fields
  • County
  • Latitude and longitude
  • Carrier route
  • Email and phone append
  • Other enabled enrichment fields
Proposed changes should be reviewed and mapped before write-back. Enhancements depend on configuration, provider availability, and purchased services. Approved fields such as latitude, longitude, county, and carrier route can be written back when mapped.
Review mockup — approve enhancements before Salesforce updates
Record Original City Updated City Latitude County Write Back
Jordan Lee Snt Louis Saint Louis 38.6270 St. Louis Yes
Ava Chen Phoenix Phoenix 33.4484 Maricopa Yes
Sam Rivera Austin Austin — — Skipped

Illustrative UI only. Users approve records and field mappings before any Salesforce Contact or Lead is updated.

Keep every interaction tied to the originating Salesforce record.

Indemption is designed to update existing Contacts or Leads when possible and create new records only when the configured workflow permits it—while preserving the source that caused the response.

  1. Retained Salesforce record ID

    When a unique QR is already tied to an imported Salesforce Contact or Lead, use that authoritative record ID first.

  2. Project mailing record or source key

    If the Salesforce ID is not available, resolve through the originating project mailing record or source key that preserved CRM identity.

  3. Reliable identifying fields such as email

    After the visitor identifies themselves, search Salesforce using reliable fields such as email before creating anything new.

  4. Create only when configured

    Match found: enhance or update the existing Contact or Lead and associate the activity.

    No match: create a new Lead or Contact only when the configured Salesforce workflow permits it.

A scan alone should not automatically create an unnecessary Salesforce Lead or Contact. Matching order and create behavior are controlled by project configuration and the Salesforce connection workflow.

Supported Salesforce capabilities

Indemption supports engagement, source context, and CRM updates for known records and new leads—not list sync alone. Availability depends on account configuration and enabled features.

CRM connection and import

  • Salesforce OAuth connection
  • Import Contacts
  • Retain Salesforce record IDs
  • Retain additional Salesforce fields
  • Map standard and custom fields
  • Preserve project source identity

Known-record engagement

  • Unique dynamic QR code per source record
  • Personalized Pit Stop
  • Scan and response context
  • Data enhancement
  • Selected field write-back when mapped
  • Campaign and project context

New-lead acquisition

  • Generic QR codes
  • Lead forms
  • Identify visitors
  • Search for an existing Salesforce record
  • Update a reliable match
  • Create a new record according to configuration
  • Preserve the originating source

Connected event delivery

  • Lead form events — available when configured
  • QR engagement events — available when configured
  • Wallet pass creation events — being introduced
  • USPS delivery milestones — available when configured
  • Email feeds and webhooks — available when configured
  • Salesforce native-app routing — available when configured
  • Wallet redemption activity — planned for a later phase

Being introduced Wallet pass creation can connect to Salesforce when that experience and connection are enabled. Wallet redemption is not available yet and is planned for a later phase.

Why this matters

A basic Salesforce connector moves records. Indemption helps you engage the Contacts and Leads you already have and build the records you need—then keeps Salesforce informed as the journey continues.

Typical Salesforce Connector

  1. Import Records
  2. Sync Fields
  3. Stops There

Indemption

  1. Engage Existing Salesforce Records
  2. Generate New Leads from Shared QR
  3. Personalize or Capture Intent through Pit Stops
  4. Retain the Authoritative Salesforce Identity
  5. Enhance and Update the Appropriate Record
  6. Preserve Project, QR, and Experience Context

FAQ

Common questions about Indemption and Salesforce.

Yes. After Contacts are imported, Indemption can create unique project-specific QR experiences tied to those source records so scans and resulting engagement stay connected to the originating Salesforce Contact ID.

Yes. Indemption distinguishes between Salesforce Contacts and Leads and can preserve the originating Salesforce object and record ID. Create and update behavior for Leads versus Contacts follows the configured Salesforce workflow.

No. A scan alone should not automatically create a Salesforce Lead or Contact. The Pit Stop can capture identifying information, search for an existing match, update that record when found, or create a new record only when the configured workflow permits it.

Matching prefers the retained Salesforce record ID, then the originating project mailing record or source key, then reliable identifying fields such as email. A new Lead or Contact is created only when the configured workflow allows it.

Yes. When Salesforce Contacts are imported, Indemption retains the authoritative Salesforce record ID so later engagement and approved write-back can target the correct CRM record.

Yes. Standard Indemption fields remain intact, and Salesforce-specific unmapped fields can be preserved and carried through the project—including exposure as additional staged CSV columns when needed.

Yes, when enrichment services are enabled and field mappings are configured. Approved enhancements such as corrected address data, latitude, longitude, county, and carrier route can be written back to selected Salesforce fields after review.

Unmapped Salesforce fields can be preserved as additional source fields and carried through the project. Staged CSV files can expose those fields as usable columns so they are not lost during campaign preparation.

Yes. A shared generic QR can be used by many visitors. Each visitor who identifies themselves through a Pit Stop can be matched to an existing Salesforce record or create a new Lead or Contact according to configuration—while preserving the campaign and QR source.

Wallet pass creation integration is being introduced and can connect to Salesforce when that experience and connection are enabled. Wallet redemption activity is planned for a later phase and is not available yet.

No. Wallet redemption is not implemented yet and is planned for a later phase. Do not expect redemption events to write back to Salesforce today.

No. Salesforce manages your customer records and remains the system of record. Indemption is the engagement layer that captures customer interactions and routes approved updates back into Salesforce.

No. Indemption is a customer engagement and attribution platform with Salesforce integration. Direct mail is one engagement channel among many—alongside print, packaging, signage, events, retail displays, brochures, flyers, digital content, QR codes, Pit Stops, offers, and wallet pass experiences.

Build your own integration

Prefer a native Salesforce Connected App when it fits. When you need a custom booking or operations system to start a tokenized Loop, use the UOCL inbound webhook from your server.

Start a Loop with the API

Engage the records you have. Generate the leads you need.

Use personalized QR experiences to deepen relationships with existing Salesforce Contacts and Leads, and generic QR experiences to turn anonymous engagement into attributed new records—with source context preserved.

Sign up free and receive 100 free credits to build your first campaign and connect Salesforce.