Overview
CRM pushback takes what Ionic knows about each of your Accounts (DS-IQ score, buying signals, ad engagement, website visits, engagement spikes, intent surges, and Target Account List membership) and writes it onto the matching Account in your Salesforce, once a day. Your sales and marketing ops teams can then report on it, build views and lists, and drive flows and scoring from it, without logging in to Ionic.
Pushback builds on the same Salesforce connection described in Connecting Salesforce to Ionic. Ionic already has to read your Salesforce data to know which company each Account represents, so pushback is an additional capability of that same integration, not a separate connection or install.
- One-way. Ionic writes into Salesforce. Values you type into these fields don’t come back to Ionic, and Ionic overwrites its own values the next time they change, so edits made directly in Salesforce don’t stick.
- Account level only. Values go on the Account object, not Contacts, Leads, or Opportunities.
- Only what changed. Each day, Ionic writes an Account only if at least one of its values changed.
- Uses the Account match you already have. Pushback writes to the same Salesforce Account your read connection already matched to a company. Matching itself happens as part of that connection, not as part of pushback.
Options for Receiving the Data
| Option | How It Works |
|---|---|
| Ionic Fields (Recommended) | Ionic creates its own fields on the Account. Labels start with “Ionic”, API names with Ionic_. This is the path we recommend for every pushback customer, including ones already receiving data through the legacy package below. |
| Legacy DemandScience Marketing Package Fields | For clients that have the legacy DemandScience Marketing managed package installed, the data is synced to a set of fields associated with that package instead. Some values are still delivered through new Ionic fields, since a handful of them have no equivalent field in the legacy package. See Keeping the Legacy Package Fields Updated below. |
Prerequisites
The only thing that has to be in place before pushback can start is the Salesforce connection itself: see Connecting Salesforce to Ionic. There’s no separate install or app approval for pushback.
The integration connection already has the access needed to write data. The access in that article’s Required Salesforce Permissions section (API Enabled and the connected user’s license) covers the base requirement. In addition, the connected integration user is automatically granted read and edit access to the new Ionic fields through the IntegrationCustomFieldVisibility permission set.
What you do need to do is make the fields visible to your own users, which is a separate step from the integration’s own access, and it can only happen after the fields exist.
The fields don’t exist until the first pushback job runs. That job is what creates them and writes the first values, so the steps below happen after we run it, not before.
Once the fields are there:
- Grant field-level security. Through a Profile, a Permission Set (Salesforce’s recommended approach, see Protect Data with Field-Level Security on Trailhead), or from the field’s own Set Field-Level Security page in Setup, which lists every profile at once.
- Add the fields to your Account page layout(s). Add them to every Account layout and record type your users work from, using whichever approach your org already uses: a new tab via Lightning App Builder (see Lightning App Builder on Trailhead), an existing section, or a classic page layout section.
Keeping the Legacy Package Fields Updated
This is only relevant if you already have the legacy DemandScience Marketing managed package installed and want to continue to manage the data from those legacy fields, instead of moving fully to the new Ionic fields. Some new Ionic fields still get created under this option too, for the values the legacy package never had.
We still recommend moving to the Ionic fields when you’re ready. Doing so means you no longer depend on the legacy package at all, so you can eventually uninstall it and have just one DemandScience package in your org instead of two.
- Package access. The Salesforce user connected to Ionic needs the terminus_mktg package license seat and the package’s Terminus_OAUTH_User permission set (read and edit access to the package fields).
- The existing legacy writer is turned off first, so the two systems never write the same fields on the same day.
- 24 of the existing package fields continue to be updated, now with Ionic data (see the Legacy Package Field column in the table below for exactly which ones).
- Fields the legacy package filled that Ionic doesn’t produce can be cleared, by default, at switch-over: ad spend, downloads, form fills, video plays, funnel stage, segments, keyword and intent-keyword fields, and most-visited pages. If you’d rather keep any of these at their current value instead, let us know and we’ll leave them alone.
- Some values will look different afterward. The legacy writer kept spike and intent values indefinitely once set; Ionic clears them once they age out (no spike in 180 days, no qualifying intent topic in 14 days), so fewer Accounts will show a current spike or intent topic than before.
We’ll review every field your reporting or automation depends on with you before switching, so nothing breaks unexpectedly.
Pushback Field List
The 35 fields in the table below are synced to your CRM daily. Counts and windows use UTC calendar days and end with the most recent full day of data (normally yesterday). The Legacy Package Field column only applies if you’re receiving data through the legacy package option above; Ionic-fields customers can ignore it.
| Category | Ionic Field | Field Definition | Values | Legacy Package Field |
|---|---|---|---|---|
| DS-IQ | Ionic DS-IQ Score | Ionic’s 0-100 score of how ready the account is to buy, from its intent and its engagement with your ads. | Whole number, 0-100. Blank when Ionic doesn’t score the account. | n/a |
| DS-IQ | Ionic DS-IQ Grade | The letter grade for that score. | A+ (90+), A (85-89), A- (80-84), B+ (77-79), B (74-76), B- (70-73), C (60-69), D (50-59), F (under 50). Blank when the score is blank. | n/a |
| Signals | Ionic Latest Signal Type | The most recent signal on the account in the last 90 days. | Peak Readiness, Hot Intent, or Buying Committee. Blank after 90 days with no signal. | n/a |
| Signals | Ionic Latest Signal Date | The day that signal was last detected. | Date. Keeps its last value even after the type clears. | n/a |
| Signals | Ionic Active Signals Count | How many signal types are active on the account right now. | 0-3. | n/a |
| Advertising | Ionic Ad Impressions (7 Days) | Ad impressions served to the account in the trailing 7 days. | Count. | Ad Impressions 7 Day Snapshot |
| Advertising | Ionic Ad Impressions (30 Days) | Ad impressions served to the account in the trailing 30 days. | Count. | Ad Impressions 30 Day Snapshot |
| Advertising | Ionic Ad Impressions (90 Days) | Ad impressions served to the account in the trailing 90 days. | Count. | Ad Impressions 90 Day Snapshot |
| Advertising | Ionic Ad Clicks (7 Days) | Clicks on your ads from the account in the trailing 7 days. | Count. | Ad Clicks 7 Day Snapshot |
| Advertising | Ionic Ad Clicks (30 Days) | Clicks on your ads from the account in the trailing 30 days. | Count. | Ad Clicks 30 Day Snapshot |
| Advertising | Ionic Ad Clicks (90 Days) | Clicks on your ads from the account in the trailing 90 days. | Count. | Ad Clicks 90 Day Snapshot |
| Advertising | Ionic Last Ad Impression Date | The last day the account was served an impression. | Date. Keeps its last value. | Last Ad Impression Date |
| Advertising | Ionic Last Ad Click Date | The last day the account clicked an ad. | Date. Keeps its last value. | Last Ad Click Date |
| Advertising | Ionic First Ad Impression Date (90d) | The earliest impression in the last 90 days. | Date. Moves forward as the window moves; blank with no impression in 90 days. | n/a |
| Website | Ionic Web Visits (7 Days) | Page views from the account in the trailing 7 days. Counts pages, not visits, so one person reading 12 pages adds 12. | Count. | Web Visits 7 Day Snapshot |
| Website | Ionic Web Visits (30 Days) | Page views from the account in the trailing 30 days. | Count. | Web Visits 30 Day Snapshot |
| Website | Ionic Web Visits (90 Days) | Page views from the account in the trailing 90 days. | Count. | Web Visits 90 Day Snapshot |
| Website | Ionic People On Site (7 Days) | Distinct visitors from the account in the trailing 7 days. One person reading 12 pages adds 1. | Count. | People On Site 7 Day Snapshot |
| Website | Ionic People On Site (30 Days) | Distinct visitors from the account in the trailing 30 days. | Count. | People On Site 30 Day Snapshot |
| Website | Ionic People On Site (90 Days) | Distinct visitors from the account in the trailing 90 days. | Count. | People On Site 90 Day Snapshot |
| Website | Ionic Website Goal Completions (7 Days) | Website goals (tracked actions you set up in Ionic) completed by the account’s visitors in the trailing 7 days. | Count. | n/a |
| Website | Ionic Website Goal Completions (30 Days) | Website goals completed in the trailing 30 days. | Count. | n/a |
| Website | Ionic Website Goal Completions (90 Days) | Website goals completed in the trailing 90 days. | Count. | n/a |
| Website | Ionic Last Visit Date | The last day the account was seen on your website. | Date. Keeps its last value. | Last Visit Date |
| Website | Ionic Last Website Goal Completion Date | The last day a visitor from the account completed a goal. | Date. Keeps its last value. | n/a |
| Engagement Spikes | Ionic Last Spike Date | The last day of the account’s most recent spike, on any Spike Model. | Date. Keeps its last value. | Last Spike |
| Engagement Spikes | Ionic Spike Status | Whether that most recent spike is the account’s first or a continuing one. | New or Repeat. | Spike Status |
| Engagement Spikes | Ionic Spike Percent | How far that spike rose above the account’s baseline. | Whole-number percent (43 means 43%). A New spike always shows 0. | Spike Percent |
| Engagement Spikes | Ionic Spike Model | The Spike Model behind that most recent spike. | Model name. | n/a |
| Engagement Spikes | Ionic Engaging On Models | Every Spike Model the account spiked on in the last 180 days. | Model names, one per line, A to Z. | Engaging On Models |
| Intent | Ionic Intent Topic | The account’s top surging topic among the topics you track: a topic in an intent delivery from the last 14 days with a score of 80 or more. | Topic name. Blank when nothing qualifies. | Intent Topic |
| Intent | Ionic Intent Score | That topic’s score. | 80-100. Blank when the topic is blank. | Intent Score |
| Intent | Ionic Last Intent Surge Date | When Ionic received the intent delivery behind the topic. | Date. Keeps its last value. Intent arrives weekly, so this can trail the surge by a few days. | Last Intent Surge |
| Lists | Ionic Account Lists | Your ready, active Target Account Lists the account is on. | List names, one per line. Long sets are cut at a whole name to fit 512 characters. | Terminus Account Lists (now holds Ionic lists) |
| Last Updated | Ionic Last Updated Date | The last day Ionic changed any value on this Account. | Date. An Account with no changes keeps an older date; it isn’t stamped every day. | Last Pushback Date |
Blank vs. Zero
- 0: The account is matched and you have that data source (an Ionic ad account, the Ionic website tag, or Signals), but there was no activity in the window.
- Blank: The account isn’t matched to a company, you don’t have that data source, or the value aged out (no spike in 180 days, no qualifying intent topic, no signal in 90 days).
- Dates: Last Ad Impression, Last Visit, Last Spike, and similar dates keep their last value after the activity ages out. The exception is First Ad Impression Date (90d), which clears.
- Spike Percent of 0: A New spike, not zero growth. Only a Repeat spike shows how far it rose above the account’s baseline.
- All five Engagement Spike fields blank together: No spike in the last 180 days. Spike Model can also be blank on its own, even when Spike Status and Spike Percent are set, if the model behind the spike never had a name in Ionic.
How the Daily Refresh Works
- Timing. One run a day, starting 14:00 UTC.
- Only changes are written. An Account is written only when one of its values changed. The rolling 7/30/90-day ad and web counts change for any account with recent activity as old days drop out of the window, so on a normal day a meaningful share of your matched Accounts gets written. That’s expected, not a sign something broke.
- The first fill can be tested on a small set of Accounts first, if you’d like to validate the data before the full rollout. Otherwise, the first fill is paced: it writes a large batch of Accounts at a time, with the rest following on the next run(s) until every matched Account is caught up.
- Late data doesn’t blank anything. If a source hasn’t refreshed (for example, a late weekly intent delivery), that group of fields keeps its last values until fresh data arrives.
FAQ
What do we need before pushback can start?
A working Salesforce connection, the same one described in Connecting Salesforce to Ionic. There’s no separate installation step for pushback itself.
Does Ionic need any extra permissions in our org to write these fields?
No additional setup on your side. The base access from Connecting Salesforce to Ionic’s Required Salesforce Permissions is everything the connection needs. When Ionic creates a new field, the connected integration user is automatically granted read and edit access to it through a managed permission set called IntegrationCustomFieldVisibility.
Can we grant field access or add fields to our layouts before the first pushback run?
Not quite before, the fields don’t exist until the first pushback job creates them. Grant access and add them to your layouts right after that first run.
How often does pushback update Salesforce?
Once a day, starting 14:00 UTC. Only Accounts whose values changed are written that day.
Can we test on a few Accounts before the full rollout?
Yes. The first fill can be scoped to a small, chosen set of Accounts so you can validate the data before we widen it to your full Account base.
We already have the legacy DemandScience Marketing package installed. Do we have to rebuild our reports?
No, if you choose to keep receiving data through those fields. Ionic writes into the same fields you already have. A few package-only fields Ionic doesn’t produce (such as ad spend, form fills, and funnel stage) are cleared by default at switch-over, though we can leave specific ones alone on request. We recommend moving to the new Ionic fields when you’re ready, since that’s the path all future development targets.
What’s the difference between Web Visits and People on Site?
Web Visits counts page views; People on Site counts distinct visitors. One person reading 12 pages adds 12 to Web Visits and 1 to People on Site.
Why is Spike Percent 0 when the account clearly spiked?
A New spike (the account’s first in a while) always shows 0. Only a Repeat spike shows how far it rose above the account’s baseline.
Why are an Account’s Ionic fields all blank?
Most likely the Account isn’t matched to a company in Ionic, which happens as part of the Salesforce connection, not pushback itself, so check its website domain. Otherwise you may not have that data source (no Ionic ad account or website tag), or the values aged out.
Can our team edit these fields or use them in our own automation?
You can use them in reports, views, flows, and scoring. You shouldn’t edit them directly, Ionic overwrites its values the next time they change.
Does pushback write to Contacts, Leads, or Opportunities?
No. Account only.
Comments
0 comments
Please sign in to leave a comment.