Account-level action nodes send accounts to campaigns, typically for ad channel campaigns such as Google Ads, LinkedIn, Meta Ads, and 6sense Display Ads. These nodes push accounts that have already been qualified by a decision node and do not require selecting individual accounts again. They consume segment syncs and affect segment sync limits. Account-level action nodes always return a set of accounts to act on.
Account-level action nodes include the following, as described on this page:
Considerations for all account-level channel action nodes
Syncing to Google Ads, LinkedIn, Meta (Facebook), and Salesforce consumes segment syncs and affects your segment sync limit. Refer to FAQ: Segment Sync Management.
Account-level action nodes must be preceded by a decision node. An account-level action node does not require you to select accounts because it is assumed that the accounts have already been qualified by a previous decision node.
You cannot use the same label text on more than one action node in a workflow.
Account-level channel action node timing considerations
Audiences pushed to Google Ads, LinkedIn, and Meta (Facebook) channels appear in the channel after the audience qualifies for the push node in a workflow. The audience syncs to the respective channel only after it qualifies for the push.
Qualification considerations
An audience qualifies for push when it contains at least one account. For example, in a workflow that pushes to LinkedIn, the audience appears in LinkedIn Ad Manager only after accounts meet the criteria and pass through the Push to LinkedIn node.
Timing considerations
The timing of the sync is influenced by the nodes that precede the push node in your workflow.
Timing is very important. For example, if a Push to Channel node follows a node that has a wait time or condition that must be met, the audience will not sync until the that happens. The audience will not appear in the channel’s campaign manager until the wait period or condition completes.
Example flow
Here is an example flow:
Segment > Decision node > Timer node wait for [30] days > Push to [Channel] Node ---> Channel campaign launches
In a scenario like the example, we recommend that you set yourself a reminder to launch your campaign 30 days after publishing the workflow, aligning with when the audience will be available in the channel.
Push accounts to Salesforce Campaign node
The Push accounts to Salesforce Campaign node sends Salesforce accounts to a Salesforce campaign. This is an alternative to pushing leads and contacts. It allows you to build audience definitions in Salesforce to push contacts to multi-channel campaigns, and to report on the accounts for which leads or contacts are pushed to campaigns. You can set this node and/or decision and timer nodes to consider campaign member status (sent, responded, waiting).
Dependencies
Integration with Salesforce.
The Salesforce campaign that you want to use with the workflow.
In Salesforce:
The organization must have accounts enabled for campaigns.
The organization must have Accounts as Campaign Members enabled. Without CampaignMember.AccountId, Salesforce cannot accept account campaign members.
The organization must have sfdc_api_v66_enabled, otherwise Salesforce will not write the AccountID on the campaign member.
The organization must have workflows-enable-account-sfdc-campaign enabled.
When you push an account to a Salesforce campaign, the contacts and leads associated with that account can be added as campaign members. This requires that you have enabled the Campaign Member Sync feature in Connected Campaigns.
The Minion registry entries include rows for manual, scheduled, and trigger execution of ACTION_PUSH_ACCOUNTS_TO_SALESFORCE.
Considerations
The Push accounts to Salesforce Campaign node can follow any node.
If multiple accounts from Salesforce match to a 6sense MID, the node pushes all matching accounts to the campaign.
Filters for both Salesforce CRM and 6sense are available.
Special cases where filters are not available:
Create Accounts → Add to Salesforce Campaign (No delay on special case)
Create Accounts → Purchase Contacts → Save to CRM → Save Campaign to CRM (Both People/Account)
Account Engagement campaigns and Salesforce campaigns are separate objects. Connecting them allows data synchronization, but it does not automatically create or enable Account Engagement campaigns for all associated contacts and leads. You would need to explicitly manage and configure the engagement campaigns for specific contacts and leads.
Properties
Node name: A brief description that displays on the node’s icon.
Description: A lengthier description of what the node does.
Destination details: Select a Salesforce campaign from the list.
Campaign member status: The status of the campaign member in Salesforce. Status will only apply to new records added to the campaign. Anyone currently in this campaign will not be updated.
Sent
Responded
Waiting
Conditions: (Optional) Filters for the node. The filter values come from the integrated Salesforce account.
Field: The field in Salesforce.
Logic for matching: Select an operator and whether to match any or all accounts. The default is Equals Any.
How do you want to select values?: Either:
Select Select individual values and the value or values from the list.
OR
Select Select value set and the value set from the list. To learn more, refer to Filter Value Sets.
If conditions are not met: You can instruct the workflow to either:
Remove audience from campaign: Remove accounts that did not meet the node entry conditions.
Leave audience in campaign: Retain accounts that met the entry conditions and push them along through this node.
Advanced options
Batch Size: Number of records per API call. Reducing the batch size increases the number of API calls, which increases processing times. The default is 200. Changes take effect the next time this action runs.
If Account exits node, do not process again for 30 days: When an account is pushed to a display ads campaign, then the workflow will not process the account again for this number of days. This allows you to control how often an account gets an ad, and not over-saturate with too many ads in quick succession. If you set this value to 0, the workflow will process the account and push it to a 6sense display ad every time it runs.
Push to 6sense Display Advertising Campaign node
The Push to 6sense Advertising Campaign node exports accounts to a 6sense display advertising campaign.
Dependencies
The Push to 6sense Advertising Campaign node requires a dedicated 6sense display ad campaign. You click a button to create or clone a dedicated campaign from this node. Then you continue setting up the new campaign in Advertising.
You cannot directly use a previously created campaign; instead, you can clone it from this node’s interface and modify it in Advertising.
The Push to 6sense Advertising Campaign node does not support contextual or visitor retargeting campaigns. These types of campaigns are not available when cloning, and you cannot configure these types of campaigns in Audience Workflows.
Tip: Ensure that the schedule for the ad campaign makes sense in relation to the schedule of your workflow.
Properties
Node name: A brief description that displays on the node’s icon.
Description: A lengthier description of what the node does.
Segment Name: A new, unique identifier for the ad campaign segment that displays in the Advertising application. This is required before you can create or clone an Advertising campaign.
Create a Campaign or Clone a Campaign: Either go to Advertising and create a new campaign or clone an existing one.
When you create or clone an advertising campaign, 6sense creates it in the Advertising Drafts folder.
After you create the campaign, its name appears in the node with a toggle next to it. If you deactivate the toggle, the workflow no longer exports accounts to that ad campaign.
If, in the future, a draft workflow display campaign node is deleted, 6sense also deletes the Advertising campaign the node previously created. If the workflow is published, the campaign is not deleted.
If Accounts No Longer Meet the Entry Conditions: You can instruct the workflow to either:
Remove audience from Display Ad: Remove accounts that did not meet the node entry conditions.
Leave audience in Display Ad: Retain accounts that met the entry conditions and push them along through this node.
For example, if you configured the prior decision node to only qualify Awareness stage accounts to be pushed to the ad campaign, then you can select Remove audience from Display Ad to ensure that any account that is no longer in Awareness stage is taken out of the campaign.Advanced options
If Account exits node, do not process again for 30 days: When an account is pushed to a display ads campaign, then the workflow will not process the account again for this number of days. This allows you to control how often an account gets an ad, and not over-saturate with too many ads in quick succession. If you set this value to 0, the workflow will process the account and push it to a 6sense display ad every time it runs.
Push to LinkedIn node
The Push to LinkedIn action node exports accounts to your LinkedIn Ads account as an audience.
Dependencies
A LinkedIn Business Manager account and LinkedIn integration. See LinkedIn Advertising and Segments for LinkedIn Ads.
Accounts in the segment must be from only one country.
After the accounts are in LinkedIn as an audience, you sign into your LinkedIn Ads account and connect this audience to a LinkedIn campaign. To learn more about what to do in your LinkedIn Ads account, see FAQs: Segments for LinkedIn Ads.
Properties
Node name: A brief description that displays on the node’s icon.
Description: (Optional, highly recommended) A lengthier description of what the node does.
Segment and campaign – Set up:
Segment nickname: A unique identifier for the ad campaign segment that displays and that you'll recognize when you're working in your LinkedIn Campaign Manager. Choose this as your LinkedIn Audience.
LinkedIn campaign name: The name of your LinkedIn campaign, to be used in 6sense reports. Make sure that the name matches the one in LinkedIn. After you enter the name, a toggle appears so that you can turn off the push to the LinkedIn campaign at any time.
(New in Aug 2026) You can use an active campaign or a draft campaign.
Sync limit notification: An information block tells you how many syncs have already been used out of your contracted sync limit.
LinkedIn Campaign Manager Account: Choose a campaign from the list of integrated LinkedIn campaigns.
If If there are no campaigns, then no integrations are functional. See FAQs: Segments for LinkedIn Ads.
The campaign you choose is active at the workflow level. You cannot use multiple LinkedIn campaigns in a single Audience Workflow.
If Accounts No Longer Meet the Entry Conditions: If this action node was preceded in the workflow by a decision node, the decision node created entry conditions (qualifications) for this node. You can instruct the workflow to either:
Remove audience from LinkedIn: Remove accounts that did not meet the node entry conditions.
Leave audience in LinkedIn: Retain accounts that met the entry conditions and push them along through this node.
For example, if you configured the prior decision node to only qualify Awareness stage accounts to be pushed to the ad campaign, then you can select Remove audience from Display Ad to ensure that any account that is no longer in Awareness stage is taken out of the campaign.
Use LinkedIn draft campaigns for filters: (New in Aug 2026) Select one or more draft campaigns to use as filters in all workflows and segments.
Advanced Options
If Account exits node, do not process again for 30 days: When an account is pushed to LinkedIn, then the workflow will not process the account again for this number of days. This allows you to control how often an account gets an ad, and not over-saturate with too many ads in quick succession. If you set this value to 0, the workflow will process the account and push it to LinkedIn every time it runs.
Best practices for the Push to LinkedIn node
Use a draft LinkedIn campaign in a Push to LinkedIn node
(New in Aug 2026) You can set up a Push to LinkedIn action node to use a downstream filter for a draft campaign in LinkedIn. This way you can set up the workflow logic in decision nodes before your LinkedIn campaigns start serving impressions. To set this up:
Create your draft campaign in LinkedIn.
Create your workflow. For example, starting with a segment, add a Sync to LinkedIn node.
In the Sync to LinkedIn node properties, name the node
(Optional) Give it a description for future reference.
Select your LinkedIn Campaign Manager account.
Select Select draft campaigns.
In the popup, select one or more draft campaigns.
Select Add to filters. 6sense adds the draft campaign to filters lists and confirms that with a popup message.
Tips:This property maps the draft campaign to the workflow.
This is a mapping, 6sense does not start the campaign in LinkedIn.
This action adds the draft campaign to both workflows and segments filters lists.
The draft campaign mapping is a placeholder, there is no engagement yet for a draft campaign.
Continue building out the workflow.
The draft campaign is available for filters at Advertising > LinkedIn Campaigns >
Reached Accounts (LinkedIn Campaign)
Engaged Accounts (LinkedIn Campaign)
For example, you can add the filter in a decision node and send the filtered campaign results to a Gong Flow.
Publish the workflow.
Tip: It takes approximately 48-72 hours for LinkedIn to sync the segment accounts for the Sync to LinkedIn node.Make your final edits the LinkedIn campaign, such as adding the segment sync as the audience and selecting the ad set.
Publish the LinkedIn campaign.
After the LinkedIn campaign is published, then the published workflow can process the accounts, according to its frequency.
Push to Meta Ads node
The Push to Meta Ads action node pushes accounts to your Facebook account as an audience.
Dependencies
A Meta Business Manager account and Meta integration. See 6sense for Meta Ads.
Properties
Node name: A brief description that displays on the node’s icon.
Description: A lengthier description of what the node does.
Segment and campaign – Set up:
Segment nickname: A unique identifier for the ad campaign segment that displays in Meta. Choose this as your Meta Audience.
Meta campaign name: The name of your Meta campaign, to be used in 6sense reports. Make sure that the name matches the one in Meta. After you enter the name, a toggle appears so that you can turn off the push to the Meta campaign at any time.
Meta Account:
You cannot use multiple Meta campaigns in a single Audience Workflow.
If Accounts No Longer Meet the Entry Conditions: If this action node was preceded in the workflow by a decision node, the decision node created entry conditions (qualifications) for this node. You can instruct the workflow to either:
Remove audience from Facebook: Remove accounts that did not meet the node entry conditions.
Leave audience in Facebook: Retain accounts that met the entry conditions and push them along through this node.
For example, if you configured the prior decision node to only qualify Awareness stage accounts to be pushed to the ad campaign, then you can select Remove audience from Display Ad to ensure that any account that is no longer in Awareness stage is taken out of the campaign.
Advanced Options
If Account exits node, do not process again for 30 days: When an account is pushed to LinkedIn, then the workflow will not process the account again for this number of days. This allows you to control how often an account gets an ad, and not over-saturate with too many ads in quick succession. If you set this value to 0, the workflow will process the account and push it to Meta every time it runs.
Push to Google Ads node
The Push to Google Ads action node pushes accounts to your Google Ads account as an audience.
Dependencies
A Google Ads account and integration. See 6sense with Google Ads.
Properties
Node name: A brief description that displays on the node’s icon.
Description: A lengthier description of what the node does.
Segment and campaign – Set up:
Segment nickname: A unique identifier for the ad campaign segment that displays in Google Ads Campaign Manager. Choose this as your Google Ads Audience.
Google Ads campaign name: The name of your Google Ads campaign, to be used in 6sense reports. Make sure that the name matches the one in Google Ads. After you enter the name, a toggle appears so that you can turn off the push to the Google Ads campaign at any time.
Google Ads Account:
You cannot use multiple Google Ads campaigns in a single Audience Workflow.
If Accounts No Longer Meet the Entry Conditions: If this action node was preceded in the workflow by a decision node, the decision node created entry conditions (qualifications) for this node. You can instruct the workflow to either:
Remove audience from Google Ads: Remove accounts that did not meet the node entry conditions.
Leave audience in Google Ads: Retain accounts that met the entry conditions and push them along through this node.
For example, if you configured the prior decision node to only qualify Awareness stage accounts to be pushed to the ad campaign, then you can select Remove audience from Display Ad to ensure that any account that is no longer in Awareness stage is taken out of the campaign.
Advanced Options
If Account exits node, do not process again for 30 days: When an account is pushed to LinkedIn, then the workflow will not process the account again for this number of days. This allows you to control how often an account gets an ad, and not over-saturate with too many ads in quick succession. If you set this value to 0, the workflow will process the account and push it to Google Ads every time it runs.
Document changelog
Aug 12 2026: Added ability to select a draft LinkedIn campaign, reformatted pages