Skip to main content

​
Why don’t my Constant Contact SMS numbers line up with my time zone?

The Constant Contact SMS API returns each campaign’s daily performance in UTC, and it does not expose a reliable per-account time-zone field. Adriel stores those daily totals exactly as the API reports them, so a workspace operating outside UTC may see a day’s numbers that don’t match the local calendar day. The effect is largest near midnight local time, where activity can land in the neighboring UTC day. Reading each daily total as a UTC day boundary keeps the interpretation consistent, and widening the date range smooths out the shift across a reporting period.

​
Why is Constant Contact SMS a separate data source from Constant Contact Email?

Constant Contact SMS and Constant Contact Email are two distinct data sources that happen to share the same Constant Contact account. They return different metrics and behave differently: SMS data is captured as a daily time series, while Email data represents lifetime campaign totals. Keeping them separate lets each surface the metrics and breakdowns that actually apply to it.
Because both data sources call the same Constant Contact account under a shared rate limit, a workspace that connects Email and SMS together on a high-volume account may notice an occasional slower sync while requests wait their turn. The data still lands on the next refresh.
To report on email campaigns from the same account, see the Constant Contact Email data reference. No. The connector reports at the campaign level. The available metrics are sends, deliveries, opens, clicks, and opt-outs, and campaigns can be grouped by campaign ID, campaign name, or date. There is no per-recipient or per-link breakdown available from this data source. For the full list of metrics and breakdowns, see the Constant Contact SMS data reference.

​
Why did my Constant Contact SMS data source disconnect and ask me to reconnect?

Constant Contact issues the tokens that authorize the connection, and it can invalidate them from its side. When the token is no longer valid, Constant Contact rejects the request with The refresh token is invalid or expired., and Adriel disconnects the data source rather than continue with credentials that no longer work. Reauthorizing the data source in Adriel restores access. Once reconnected, the next sync brings the SMS metrics back up to date. If the same account also has Constant Contact Email connected, that data source authorizes separately and may need the same treatment.

​
How much SMS campaign history does Adriel import when I first connect?

Adriel imports up to the previous 90 days of SMS campaign data when the data source is first connected. Because Adriel caches the data, the longer the data source stays connected, the more historical data is stored, so coverage grows day by day from the connection date forward. Campaign activity that predates the initial import window is not available from the Constant Contact SMS API for later retrieval.

​
Why do some deleted SMS campaigns disappear from my dashboard?

When an SMS campaign is removed inside Constant Contact, it stops being returned by the API, so it no longer appears in future refreshes. Adriel reports on the campaigns the platform currently returns and does not reconstruct campaigns that have been deleted at the source. Keeping campaigns in Constant Contact preserves their reporting in Adriel.

Constant Contact SMS data reference

Metrics, breakdowns, refresh cadence, and limits for the SMS data source.

Connect Constant Contact SMS

Authorize and set up the Constant Contact SMS data source in Adriel.

Constant Contact Email data reference

Email campaign metrics on the same Constant Contact account.