Skip to main content

Private offers field mapping best practices (Legacy)

Use these best practices to successfully map fields for each marketplace when using the Tackle-Salesforce integration for private offers.

Leslie avatar
Written by Leslie
Updated over a month ago

Legacy version:

This feature is an older version of the Tackle for Salesforce integration (versions 1.49 and earlier) that will soon no longer be supported. If you have questions or want to upgrade to the latest version, contact [email protected].

How to use the mapping tables

The field mappings are displayed across three tables:

Each table displays the following information:

  • Tackle label - The name of the field in Tackle

  • Recommended mapping - Known best practices for mapping field values

Common fields

These fields have common mappings across all clouds.

Tackle label

Recommended mapping

Cloud Marketplace Listing

Select the listing that you’d like to use for private offers. If more than one, then leave blank.

Marketplace Fee

Select your Marketplace fee. This is optional and is used to provide you with the correct Net Contract Value on any Tackle order notifications.

Duration

Select the duration of your contract.

Offer Acceptance Deadline

The latest date that your buyer has to accept the private offer.

Buyer Detail

The contact from your buyer that has permissions to accept the private offer.

Notification Recipient Email

The stakeholders you want to inform about private offers. You can include people in or outside your company. Added contacts will receive an email notification with details about the offer, including once it’s accepted.

Customer Metadata Fields

Create key value pairs for any additional custom data fields that you’d like to be included on your Tackle bookable artifact for your finance and operations teams.

AWS-specific fields

These fields are used specifically for AWS Marketplace private offers to map for each cloud.

Tackle label

Recommended mapping

Offer Type

The type of private offer you’d like to create, either ‘Direct’ for direct to buyer or ‘Partner’ for resale authorizations.

Payment Model

Either ‘Per Product’ or ‘Payment Schedule’. Learn more about payment models for AWS.

Billing Term

This is the start time of the offer. Options are to ‘Start On Acceptance’ or ‘Future Dated’ for future dated agreements (FDAs).

Start Date

Only applicable for ‘Future Dated’ billing terms. This is the start date for a future dated agreement.

End Date

Applicable for ‘Future Dated’ billing terms and Amended Offers. This is the end date of the contract.

Max Service Start Date

For partner private offers only. This is the max or latest date that a partner can use as a start date for their partner private offer.

Price Per

Only applicable for ‘Per Product’ payment models, this is the price per unit of each dimension.

Dimension Name (SKU)

Recommended to map to the Opportunity Line Item Product Name.

Dimension API Name

Recommended to map to the Opportunity Line Item Product.

Quantity

The number of units for each dimension.

Buyer AWS Account Number

The AWS Account Number that your buyer will purchase from.

Partner AWS Account Number

For partner offers, the AWS Account Number partner that you will authorize to create a private offer.

AWS EULA Version

Your preferred contract type for this offer. Either the EULA from your Public Listing, the AWS Standard Contract, or a custom contract for this specific offer.

Reseller Agreement Type

Your preferred Reseller Agreement type for partner offers. Either ‘no thanks’, the standard Reseller contract for AWS marketplace (RCMP), or a custom contract for this specific offer.

Microsoft-specific fields

These fields are used specifically for Microsoft private offers to map each cloud.

Tackle label

Recommended mapping

Tenant ID

The Microsoft Tenant ID where your buyer will set up their subscription.

Billing ID Account

The Microsoft Billing Account ID that you’d like to send private offer pricing to.

Start Date

The optional start date if the offered pricing should start on a date other than the accepted date. Start date will always be the first of the month. You can map to Date Fields if needed.

End Date

The end date for when the offering pricing will expire. This will always be the last day of the month. You can map to Date Fields if needed.

Did this answer your question?