# How to align marketing and sales using Salesforce integrations

Alignment is a shared definition of a qualified account and one owner of the stage. A field sync without that definition schedules the argument.

**Published:** 2025-10-29
**Canonical:** https://synconai.com/align-marketing-and-sales-salesforce
**Author:** SynconAI Architecture Team

## In short

Marketing and sales are aligned when both sides use one definition of a qualified account and one person owns the lifecycle stage. An integration that copies fields without that definition delivers the disagreement on a schedule. Name the object, the field, and the owner before anything syncs. An agent will repeat whichever stage is stored on the record it can read.

## Sources

- **About Salesforce Data 360** (retrieved 2025-10-14)
  https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud.htm&type=5
  > As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you may see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remains unchanged.
- **Agentforce: What is an AI agent?** (retrieved 2026-10-10)
  https://www.salesforce.com/agentforce/
  > These agents generate responses that are consistent with your company’s brand voice and guidelines using trusted business data, including Salesforce CRM data, external data from Data 360, and more.

## What to take away

- Write one definition of a qualified account that both teams will use on a Monday.
- One person owns the lifecycle stage. Everyone else proposes a change.
- A sync that overwrites the stage each hour industrialises the argument.
- Agents repeat the value on the record. Two stages means a confident answer about one of them.

## The guide

A form lands on Thursday. The marketing flow sets the account to Qualified, because a submitted form is what that team means by the word. Sales had moved the same account to Working on Wednesday, after three meetings and no budget. At the top of the hour the integration writes Qualified back. The forecast extract reads that field and puts the account in the quarter. On Monday the room argues about the accounts that flipped. A new seller asks an agent whether the account is qualified. The agent says yes. The seller starts a quote. On Friday sales leadership takes the account out of the forecast. The quote is scrap. The hours in that loop are the cost.

The integration did not create the disagreement. It scheduled it. Alignment is a sentence both teams will say the same way. What makes an account qualified. Which object holds that fact. Which field holds the lifecycle stage. Which person is allowed to change it. An integration that copies fields without those four lines does not create agreement. It delivers the fight faster, to more people, including anyone who asks an agent.

## One definition, written where the work happens

Pick ten accounts that became customers and ten that died in the last two quarters. Sit marketing and sales in the same room. For each account, each team marks the stage they believed applied at the handoff, and the date they believed the handoff happened. Where the marks differ, do not average them. Write the rule that would have made both marks the same.

The rule has to be decidable from fields you already store, or from a field you are willing to add and have someone fill. "They felt ready" is not a rule. "A form was submitted" is a rule, and it is often the wrong one, because a form records that someone asked for information. "A meeting was held and a budget figure was written on the opportunity" is a different rule. "A score crossed a threshold" is a third. You are allowed one of them as the meaning of this field. The others can exist as their own fields, with their own names, so a report can still show interest without calling it a handoff. They cannot share the word qualified.

Write the chosen rule in three places, in the same words. The field definition. The help text a new seller reads on the page. The integration write condition, so a flow that does not meet the rule cannot update the field. If you cannot finish the sentence, you are not ready to sync. Shipping the sync anyway means the argument will be conducted in field history, every hour, until someone turns the job off in a hurry and the last write wins by accident.

Read the sentence against the ten accounts that died. If the rule would have called them qualified, the rule is describing interest, not a handoff sales can work. Interest is a real fact. Store it under a name that says so. Qualified, in this design, means the moment sales accepts the account into its working set. Marketing can propose that moment. Marketing does not declare it by overwriting the field when a campaign ends.

## One object, one field, one owner

The stage lives on one object, in one field. Say which, out loud, in the same meeting. On many business-to-business orgs the fight is happening twice: once on an account lifecycle, once on an opportunity stage, because both fields have been asked to answer "how real is this." They can both exist when they mean different things. The account field answers whether this company is in a selling motion with you. The opportunity field answers whether this particular deal has a close plan. The failure is two fields that claim the same answer. People then pick the one that supports the number they already wanted.

A second field called final stage, and a third called stage confirmed, is how reports start choosing at random. Delete down to the field the sentence names. Point both teams at it. A dashboard that still shows the marketing stage beside the sales stage is keeping the argument on the wall, and every meeting will re-litigate which tile is "the real one."

One person owns that field. The owner is a name, not a committee and not a shared mailbox. Other teams may propose a change. They write the proposal on a field that does not drive the forecast, or they ask. They do not overwrite the stage from their own flow because a campaign ended, because a seller moved a meeting, or because a score recalculated overnight. The owner accepts or refuses. Field history shows that user's name on the change. That is the job. An owner described as "both teams" is nobody, and when the hourly job runs, nobody is there to refuse it.

Put the name in the field description, in words a new seller can read without a briefing. The description says who decides and what the decision means. If it says the field is synced from marketing, you have named a system. Systems do not accept or refuse. They repeat the last payload.

:::note
Account lifecycle and opportunity stage can both be true. They cannot both be the definition of qualified. Write the sentence for one field, and give the other field a different name.
:::

## The integration copies what you failed to decide

[Data 360 help](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud.htm&type=5) records a rename, not a definition: "As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you may see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remains unchanged." Update the diagram to the current name. The rename does not decide what qualified means. Old labels in the application are the same product. A map that still points at a field you stopped filling will write the stage somewhere nobody reads, and the field the forecast uses will keep the old fight.

Bringing the stage into Data 360 before the sentence exists copies the disagreement into a second store. Putting two stage fields under a new label does not reconcile them. It gives you a third place to be wrong, and a segment, a dashboard, or an agent can prefer any of the three without telling you which sentence it used. The release that helps is the one that deletes a duplicate field. Do that before you add another campaign tool, another form, or another score. A new source of the word qualified, with no owner, is another voice in the same argument, on a faster clock.

## The agent repeats the value you stored

Salesforce says these agents generate responses "using trusted business data, including Salesforce CRM data, external data from Data 360, and more." An agent will repeat the stage it finds. If the marketing value and the sales value both exist, the reply can sound sure about whichever one retrieval returned. The seller on the other end of that reply cannot see the field history. They hear one sentence and start work from it. Fix the stored value. Do not add a paragraph of instructions asking the agent to reconcile a fight the teams have refused to have in the room. An instruction that says to prefer the sales stage is an admission that two stages are still stored. Delete one of them.

The same split shows up on a forecast call. The agent summarises qualified pipeline from the field the prompt named, or from the field it found first. Two calculations means two meetings. The agent will contribute to both, sounding equally sure. The cure sits upstream of the prompt. One field. One sentence. The prompt can then be short, because there is nothing left for it to adjudicate.

## Stop the sync that flips the same accounts

When a flow writes one team's stage over the other's every hour, you have scheduled the argument. Turn that write off. For a fortnight, log what it would have overwritten, and do not let it overwrite. If the same accounts would flip more than once, you do not have a timing problem. You have two definitions. Go back to the ten-account exercise. Turn the sync on again for that single field, and only in the direction the owner allows.

Direction matters more than frequency. A one-way write from the owning team, applied when the rule is met, is a publication of a decision already made. A two-way write is a debate with a timer. Marketing can still fill a proposal field. A seller can still move an opportunity stage that means a different fact. Neither write is allowed to land on the lifecycle field unless the owner is the one the automation represents, and the rule in the help text is the condition on the flow.

Watch the log for three patterns that hide inside "just a sync." A campaign-end flow stamps every respondent as qualified, including people who became customers years ago and people who asked not to be contacted. A scoring job promotes and demotes the same account every night because the score sits on the threshold and chatters. A seller flow sets the stage when a meeting is booked, and a marketing flow sets it back when that meeting campaign is marked complete. Each of these is a write condition that was never shown the sentence. The fortnight log shows them without waiting for the next Monday meeting to discover them in the forecast.

:::warn
If the same accounts would flip more than once, leave the write off. Another mapping into Data 360 will not settle a field two automations are fighting over.
:::

| Decision | Write it as | Still blocked while |
| --- | --- | --- |
| What qualified means | One sentence both teams can apply to a named account | The twenty accounts still produce two marks |
| Where it lives | One object and one field | A second stage field is on the forecast |
| Who changes it | One named person in the field description | A flow from the other team updates it |
| What others may do | Propose on a field that is not the stage | Their automation overwrites the stage |
| What an agent may repeat | That field alone | Two values are both available to retrieve |

## What is cheap now, and what will not be

Cheap, while nothing downstream treats the field as fact: the wording of the sentence, which accounts you used as the test, the help text, the name in the description. Do these in the room. They are the work, and they are a few hours with the right people.

Expensive once the field feeds a forecast, a pay plan, a segment, or an agent prompt: changing what qualified means. Every historical value was written under the old sentence and will be read under the new one. Last quarter becomes incomparable, and nobody can say which sentence a given row used. If the meaning must change, start from a date. New values follow the new sentence. Old values stay, with the old sentence written beside the report. A silent redefinition looks like a data fix and behaves like a restatement of history.

Three ways teams skip the room. They sync first and agree the definition in a later phase, which means the definition is whatever the last write left behind. They let each region keep a local qualified field, then ask for one global number, and discover four sentences wearing one column header. They add an agent so it can explain the difference, which turns the difference into a paragraph a seller will treat as fact. None of these is a smaller version of the exercise. Each defers it until the field history is longer and the quote has already been built.

## What you can check on Monday

Open the field history on the stage for twenty live accounts. If the history is a conversation between two integrations, you do not have alignment. You have a log. Name the owner in the field description. Point both teams' reports at that field alone. After the sync has been back on for a week, in one direction, read the same twenty histories again. If the changes are now decisions by the owner, the sentence is holding. If a campaign job appears as the user on the history, the write condition was not applied, whatever the design document says.

The stage is also a box on the journey. A slide that says qualified and names no record is the same gap in poster form. The object-level version of this argument is [the B2B map that names the record at each stage](/map-b2b-customer-journey-salesforce). If the map and the field disagree about where qualified lives, fix one of them before either is used in a steering pack.

## Questions

### What has to be agreed before marketing and sales sync?

One sentence for what a qualified account is, which both teams can apply to a real account on a Monday. The object and the single field that hold the lifecycle stage. The named person who may change that field. Other teams can propose a change on a field that does not drive the forecast. They do not overwrite the stage from their own flow because a campaign ended or a meeting was moved. If the sentence is not finished, the sync is not ready to turn on.

### Why does a two-way field sync make the dispute worse?

It copies both versions on a schedule. The teams still disagree about what qualified means. They meet that disagreement every hour, in the forecast, in every report that reads the field, and in any agent that repeats the stored value. A one-way write from the owning team, when the rule is met, publishes a decision already made. A two-way write is a debate with a timer. Log what the job would overwrite for a fortnight before you let it write again.

### Does the Data Cloud rename settle the definition?

No. Salesforce says: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." The same page says the functionality and content remains unchanged. Update the name on the diagram. Qualified is still the rule you write, on one field, with one owner. A new label does not decide which team is allowed to change the stage.

### What will an agent say if two stages are stored?

Salesforce says agents answer using trusted business data, including CRM data and Data 360. The agent will repeat a value it can read. If two values disagree, it can sound sure about one of them, and the person hearing the reply will not see the field history behind it. Fix the stored value so only one stage remains. An instruction that tells the agent to prefer one of them admits the fight is still on the record.

### When should we turn the sync back on?

After the owner and the rule are written in the field definition, the help text, and the write condition. After you have watched, for a fortnight, what the job would have overwritten. Resume for that one field, in the direction the owner allows. Leave duplicate stage fields off the report and off the forecast. If the same accounts would have flipped more than once, go back to the ten-account exercise before you enable the write.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Marketing Cloud Next (https://synconai.com/salesforce-marketing-cloud-next).