Salesforce conversion records

Upsert identified Nimriz conversions into a dedicated Salesforce custom object through managed authorization.

Salesforce setup is available only when it appears in your workspace's destination catalog.

Requirements

• A Professional plan or higher.
• The Nimriz External Client App package installed in the Salesforce org.
• A Nimriz_Conversion__c object with Nimriz_Delivery_ID__c configured as a unique External ID.
• API access and create/update permission for the object fields.

Create the Salesforce object

Create a custom object with the exact API name Nimriz_Conversion__c, without a namespace prefix. Set its record name to Auto Number because Nimriz does not send a Name value. Add every field below using the exact API name, and give the connected Salesforce user read, create, and update access as applicable.

Use Text length 255 for the identifiers and short text fields. For customer IDs, URLs, and UTM values, choose a length that covers your actual values; use Long Text Area when values exceed 255 characters. Set the Number field's precision and decimal places to accommodate the conversion values you send. Salesforce documents these choices in Custom Field Types.

All listed fields must exist. Allow attribution fields to be blank, and leave conversion value and currency optional. Nimriz does not shorten values to fit your field lengths or convert amounts to your Salesforce org currency. Keep the supplied currency in Conversion_Currency__c. Avoid extra required fields without defaults, since Nimriz will not supply them automatically.

If you add custom property mappings, create each mapped custom field and grant write access before testing. Do not map over the delivery ID or the standard fields above.

Connect Salesforce

1. Create the documented object and fields in the production or sandbox org.
2. Go to Integrations›Destinations›Browse catalog and choose Salesforce.
3. Choose Production, Sandbox, or a validated My Domain host and save the disabled destination.
4. Select Connect provider and approve the api and refresh_token scopes.
5. Enter a temporary sample customer ID and send a test. The test checks the delivery ID field and creates or updates a real sample record. Inspect the record and its field values in Salesforce.
6. Enable the destination after the current configuration and connection pass.

Nimriz upserts by delivery ID, so retrying the same delivery updates the same record. Only conversions with your customer external ID qualify. Raw IP and complete User-Agent values are not sent. Before using the destination for your workflow, check a representative conversion with your longest text values and expected numeric precision, including a conversion without optional values.

Troubleshooting

• Schema mismatch: verify the object, unique External ID, and documented writable fields.
• Reconnect required: reconnect the org and send another test.
• Permission denied: grant object and field permissions to the connected Salesforce user.