Salesforce connector in Allocadia — per-FY user setup pattern

The Allocadia Salesforce Connector syncs campaign/opportunity data. Some legacy setups use a per-FY integration user — here's why and how.

What the connector does

The Allocadia Salesforce Connector pulls Salesforce campaign and opportunity data into Allocadia, where it can be referenced from Line Items, used in reporting, or linked back to spend records. Common data flows:

• Salesforce campaigns → Allocadia Line Items (one-to-one or one-to-many).
• Opportunity amounts → Allocadia for pipeline-attached reporting.
• Custom-field sync both directions.

The connector authenticates against Salesforce using OAuth and against Allocadia using a dedicated integration user with API access.

The per-FY user pattern

Historically, some Allocadia accounts configured the connector with a per-fiscal-year integration user — e.g. customer.connect.fy26@customer.com for FY26, customer.connect.fy25@customer.com for FY25. Reasons teams did this:

• Scoping — each year's integration user is granted access only to that FY's hierarchies, limiting blast radius.
• Auditability — the per-FY user makes it obvious which year's integration took which action.
• Clean handoffs — new FY, new user; old year's user is deactivated at close.

If your account uses this pattern, the connector configuration is updated each year during rollover to point at the new user. Your admin or CSM manages the rotation.

Modern setups

Most newer accounts use a single long-lived integration user rather than per-FY users. The single-user pattern is simpler to maintain and relies on hierarchy-level permissions rather than user segmentation to control access.

If you're setting up Salesforce integration fresh, the single-user pattern is typically recommended. Talk to your CSM about which pattern fits your governance model.

Troubleshooting

If the connector fails after a rollover:

• Confirm the integration user still has API access and a valid password.
• Confirm the user has permission on the new FY hierarchy.
• Check Workato (or whichever platform runs the recipe) for the specific error.

See Our Workato integration with Allocadia is failing — common causes.

Related articles

• Common integration patterns in Allocadia — Workato, SFTP, SFDC, file-based
• Our Workato integration with Allocadia is failing — common causes
• The Allocadia REST API — overview of endpoints
• Does my SSO user need a separate password to use the Allocadia API?