Documentation: Impact API Connector

Set up reliable server-side impact.com conversion reporting for WooCommerce, including attribution capture, automatic retries, promo-code matching, backfills, delivery status, privacy controls, and searchable logs.

1) Overview

Impact API Connector sends eligible WooCommerce conversions directly to the impact.com Conversions API.

The plugin is designed to work alongside the normal Impact WordPress plugin or Universal Tracking Tag:

Your existing Impact integration handles inbound affiliate tracking.
Impact API Connector stores trusted attribution on the WooCommerce order.
The connector submits the conversion from WordPress when the order has been paid.
Delivery results are recorded on the order and in a searchable log.
Temporary failures can be retried automatically.
Automatic reconciliation and manual backfills can recover eligible orders that were not successfully reported.

This gives your store an auditable server-side conversion workflow instead of relying entirely on a browser-side purchase event.

Impact API Connector supports:

Classic WooCommerce checkout
WooCommerce Cart and Checkout Blocks
High-Performance Order Storage
Impact ClickId attribution
Impact partner promo-code attribution
New-versus-existing customer classification
Automatic retries and reconciliation
Manual order resends
Bulk historical backfills
Standard and minimized data modes

2) Requirements

Impact API Connector requires:

WordPress 6.7 or newer
WooCommerce 8.2 or newer
PHP 7.4 or newer
An active impact.com advertiser account
An Impact Account SID and Auth Token
A Campaign ID
At least one supported conversion event identifier
A functioning WordPress scheduled-task system
An existing Impact link-tracking implementation

The plugin is tested with WordPress through version 7.1 and WooCommerce through version 11.1.

HTTPS is strongly recommended because the plugin handles affiliate attribution, order information, and API credentials.

Impact API permissions

The configured Impact credentials must be able to submit conversions.

If you use the local partner promo-code registry, the credentials must also have permission to read promo codes for the selected campaign.

Scheduled tasks

The plugin uses WooCommerce Action Scheduler for delayed order processing, retries, automatic reconciliation, promo-code synchronization, and bulk backfills.

Scheduled actions can normally be inspected under:

WooCommerce → Status → Scheduled Actions

WordPress must receive traffic or have a server-side cron runner so scheduled work can execute consistently.

3) Understanding the two-part Impact setup

Impact API Connector does not replace inbound affiliate tracking.

A complete setup has two parts:

Inbound attribution: The normal Impact plugin or Universal Tracking Tag recognizes the affiliate visit and makes the ClickId available.
Conversion delivery: Impact API Connector saves trusted attribution on the WooCommerce order and submits the paid conversion to Impact.

Keep your normal Impact integration enabled for inbound tracking.

If that integration also reports browser-side purchase conversions, disable that purchase event before enabling conversion sending in Impact API Connector. Otherwise, the same WooCommerce order could be reported through both browser-side and server-side integrations.

Important: Impact API Connector improves conversion delivery and recovery, but impact.com still makes the final decision about attribution, deduplication, commissions, and whether a submitted conversion qualifies under your program rules.

4) Installation

Download the Impact API Connector ZIP file.
In WordPress Admin, go to Plugins → Add New Plugin → Upload Plugin.
Select the plugin ZIP.
Click Install Now.
Click Activate Plugin.
Open WooCommerce → Impact API Connector.

WooCommerce must already be installed and active. If WooCommerce is unavailable, Impact API Connector will not activate.

Activating your license

The Syllable Agency licensed build initially displays only the License tab.

Open WooCommerce → Impact API Connector → License.
Enter your purchase license key.
Click Activate license.
Wait for the page to confirm that the license is active.

After successful activation, the remaining connector tabs become available.

An active license enables:

Attribution capture
Conversion submission
Automatic retries
Scheduled reconciliation
Promo-code synchronization
Bulk backfills
Order-level resend tools
Impact status indicators
Licensed plugin updates

Deactivating a license

To release the license from the current site:

Open the License tab.
Click Deactivate license.
Confirm that the status changes to inactive.

Deactivation clears the saved license key and stops the connector’s operational features and scheduled work.

5) Quick start

For a standard installation:

Activate the plugin license.
Open the Connection tab.
Enter your Impact Account SID and Auth Token.
Enter the Campaign ID.
Enter at least one event identifier.
Choose Standard mode or enable HIPAA mode.
Enable conversion sending.
Save the Connection settings.
Open Promo Codes and queue the first synchronization.
Open Automation and review the recovery settings.
Place an attributed test order.
Confirm the result from the WooCommerce Orders screen and Logs tab.

Do not enable conversion sending until duplicate browser-side purchase reporting has been disabled.

6) Connection settings

Connection settings are located at:

WooCommerce → Impact API Connector → Connection

The page shows either Configured or Configuration incomplete.

Conversion sending cannot remain enabled unless all minimum connection fields are complete.

Enable conversion sending

Activates order processing, conversion submission, retries, promo-code synchronization, and backfills.

New installations begin with conversion sending disabled. The checkbox will not remain enabled unless the required connection fields have been provided.

Disabling conversion sending suspends connector-owned background work. Saved configuration and logs remain available.

Account SID

Enter the Account SID for the applicable impact.com advertiser account.

The Account SID is used as part of the API endpoint and authentication request.

Auth Token

Enter the Impact API authentication token associated with the Account SID.

The token is encrypted before it is stored in the WordPress database. After saving, the plugin displays a placeholder indicating that the token is stored; it does not display the original token again.

To replace the token, enter a new value and save the settings.

To remove it:

Select Clear stored token.
Save the Connection settings.

Campaign ID

Enter the Impact campaign associated with these WooCommerce conversions.

The same Campaign ID is used when synchronizing partner promo codes.

Event identifiers

Configure at least one of the following:

Event Type ID
Action Tracker ID
Event Type Code

The appropriate value depends on how the conversion event is configured in your impact.com account.

You may provide more than one supported identifier if required by your account configuration.

Data sharing and HIPAA mode

The Connection tab lets you choose between the standard conversion payload and the minimized HIPAA-mode payload.

Standard mode

Standard mode can send Impact-supported reporting fields such as:

Campaign and event identifiers
Order ID
Event date
Conversion amount
Currency
Customer status
ClickId or promo code
Opaque customer identifier
SHA-1 hashed customer email
IP address
Browser user agent
Billing geography
Payment method
Order and product details

Names, street addresses, and telephone numbers are not added as unsupported conversion fields.

The request and response can also be stored in the plugin’s private conversion log.

HIPAA mode

When HIPAA mode is enabled, the outgoing request is restricted to:

Campaign and event identifiers
Event date
Order ID
Amount
Currency
Customer status
ClickId or promo code

The following information is removed from both the outgoing payload and the connector’s request log:

Customer identifiers
Email address
IP address
Browser user agent
Billing location
Payment method
Product and line-item details

Important: HIPAA mode is a technical data-minimization control. It does not, by itself, make a website, business process, vendor relationship, or impact.com account HIPAA compliant.

7) Automation settings

Automation settings are located at:

WooCommerce → Impact API Connector → Automation

These settings control reconciliation, retry-related behavior, API timing, companion coupon requests, custom paid statuses, and failure emails.

Automatic backfill

Periodically scans recent paid orders that do not have a successful Impact delivery marker.

Automatic backfill is enabled by default once the connector is configured and active.

Disable it if reconciliation is handled by another operational process. Manual bulk backfills remain available independently.

Backfill frequency

Controls the number of hours between automatic reconciliation scans.

Default: 24 hours
Minimum: 1 hour
Maximum: 720 hours

Saving a different frequency replaces the existing recurring schedule.

The frequency should normally be shorter than the automatic lookback window so each paid order has more than one opportunity to be examined.

Automatic lookback

Controls how far into the past each automatic reconciliation scan searches.

Default: 14 days
Minimum: 1 day
Maximum: 365 days

The scan focuses on eligible paid orders that do not already have a successful-send marker.

Orders per batch

Controls the number of orders retrieved during each backfill query.

Default: 50
Minimum: 10
Maximum: 250

A smaller batch can reduce the load on stores with limited server resources. A larger batch can help high-volume stores move through a large date range more quickly.

Actual backfill processing is divided into smaller background chunks so one request does not need to process the entire job.

API timeout

Controls how long an individual Impact API request may remain open.

Default: 20 seconds
Minimum: 5 seconds
Maximum: 60 seconds

Increasing the timeout can help when the Impact API or network is responding slowly, but very long synchronous requests can tie up PHP workers. Twenty seconds is a sensible starting point.

Send companion coupon request

When an order has both a trusted ClickId and an eligible coupon, the connector sends the ClickId request first.

If this setting is enabled, it then sends a coupon-only companion request using the same WooCommerce order ID.

Impact can use the shared order ID when applying its own attribution and duplicate-handling rules.

Disable this setting if your Impact configuration should receive only the primary ClickId conversion.

Additional paid statuses

WooCommerce normally identifies paid orders through its standard paid statuses and payment date.

If your store uses custom post-payment statuses, enter their slugs as a comma-separated list. Examples might include:

intake,review,filling

Use the status slug rather than the human-readable label.

Do not add statuses that can be reached before payment. Doing so may make unpaid orders eligible for conversion submission.

Email failures

Enable this option to send an email when an Impact API error is recorded.

This supplements the order notes and conversion log; it does not replace them.

Notification email

Enter the address that should receive failure notifications.

If left empty, the plugin uses the WordPress administration email address.

Email delivery depends on the site’s normal wp_mail() configuration. For production stores, a properly configured transactional email provider is recommended.

8) Promo Codes

Promo-code tools are located at:

WooCommerce → Impact API Connector → Promo Codes

The connector synchronizes partner-assigned promo codes from the configured Impact campaign and stores them locally in WordPress.

Local storage allows coupon eligibility to be checked without making a Promo Codes API request during checkout or order processing.

Initial synchronization

After completing the Connection settings:

Open Promo Codes.
Click Queue sync.
Wait briefly for Action Scheduler to process the job.
Refresh the page.
Confirm that the status displays Registry current.
Confirm that the expected number of assigned promo codes appears.

The button queues background work. It does not keep the browser request open while every API page is downloaded.

Automatic synchronization

When registry filtering is enabled, the plugin schedules a promo-code synchronization once per day.

The registry is considered stale after 48 hours without a successful refresh.

Searching the registry

Use the search field to find a stored promo code or partner.

The table displays:

Code
Partner
Campaign
State
Start and end dates
Whether the record belongs to the current registry snapshot

Historical records are retained so a backfilled order can be evaluated against the promo-code assignment that existed on the order date.

Coupon handling modes

Use the Impact promo-code registry

This is the recommended mode.

Only coupons associated with an Impact partner and active for the order date are eligible for coupon attribution.

Matching uses WooCommerce’s case-insensitive coupon normalization. For example, SAVE10, save10, and Save10 are treated as the same code.

Send every order that uses a coupon code

This mode bypasses registry filtering and submits coupon attribution for every WooCommerce order containing a coupon.

Impact may ignore codes that are not associated with the affiliate program.

ClickId attribution is not suppressed by either coupon mode.

Fail-open behavior

If the registry is missing, stale, associated with different connection settings, or unavailable because synchronization failed, coupon filtering fails open.

That means an eligible coupon-bearing order can still be submitted rather than being silently discarded because the local registry could not be trusted.

The Promo Codes page displays a warning when this behavior is active.

9) Attribution behavior

Impact API Connector can recognize trusted attribution from landing parameters, first-party cookies, and compatible order metadata.

Recognized landing parameters include:

im_ref
irclickid
impactclickid
ImpactClickId
ClickId
clickid

When a valid ClickId is found, the connector stores it in a first-party cookie for up to 90 days.

The plugin’s cookie is:

HTTP-only
Secure when the site uses HTTPS
SameSite Lax
Scoped using the site’s configured WordPress cookie path and domain

At checkout, the ClickId and its source are copied to the WooCommerce order.

Both classic checkout and Checkout Blocks are supported.

Attribution is stored on the order

Retries, manual resends, and backfills use attribution saved with the order.

They do not use the current administrator’s browser cookie. This prevents an administrator’s own Impact session from contaminating a historical resend.

Generated direct-tracking identifiers

Some Impact integrations can generate identifiers beginning with ~cglic during checkout.

Impact API Connector ignores these values by default because their presence alone does not prove that a commissionable partner click occurred.

A developer filter is available to change this behavior, but it should only be enabled when the site’s attribution design has been reviewed carefully.

10) Conversion processing and retries

An order becomes eligible when:

The connector is licensed, enabled, and completely configured.
WooCommerce considers the order paid, or its status is included under Additional paid statuses.
The order has a trusted ClickId or eligible coupon.
The order has not had its connector-owned personal data erased.
The conversion is not already marked as sent, unless an administrator deliberately forces a resend.

The connector responds to WooCommerce payment and paid-status events. It also schedules a delayed post-checkout check because some gateways finalize payment after the checkout request has ended.

Successful responses

An eligible 2xx response with a supported successful status is recorded as sent.

Impact responses with Status=QUEUED are also treated as accepted because Impact has accepted responsibility for processing the conversion.

The plugin then:

Stores the successful-send time on the order.
Clears previous retry and error markers.
Records the result in the conversion log.
Adds a private order note.
Stores an Impact action identifier when one is returned.

Automatic retries

The plugin automatically retries transport failures, HTTP 429 rate limits, and HTTP 5xx server errors.

The retry schedule is:

Five minutes after the first failure
Fifteen minutes after the second failure
One hour after the third failure
Six hours after the fourth failure

After five failed attempts in total, automatic retries stop and the order is marked for manual review.

Permanent-looking client errors are recorded but are not repeatedly retried automatically.

11) WooCommerce order status

Impact API Connector adds an Impact column to both the legacy and HPOS WooCommerce Orders screens.

Gray

No trusted Impact ClickId or eligible coupon was found, so no conversion needs to be sent.

Gray can also indicate that connector-owned personal data was erased and future submission is disabled.

Yellow

The order has eligible attribution and is waiting to be sent or retried.

The tooltip indicates whether the order is awaiting its first send or was placed in the processing queue.

Green

Impact accepted the conversion.

This includes immediately confirmed conversions and supported queued responses.

The tooltip displays the recorded send or acceptance time.

Red

The most recent conversion attempt produced an error.

Hover over the icon for a short description, then inspect the order notes and Logs tab for the full result.

12) Manually resending an order

Administrators with permission to manage WooCommerce can deliberately resend an eligible order.

Open WooCommerce → Orders.
Open the applicable order.
Find the Order actions panel.
Select Resend to Impact.
Apply the action.
Review the new private order note.
Confirm the result in the Impact column or Logs tab.

A manual resend can submit an order that was previously marked successful. Use it only when there is a reason to believe another request is needed.

The action is unavailable when:

The current user cannot manage WooCommerce.
Conversion sending is disabled.
API configuration is incomplete.
Connector-owned personal data was erased from the order.
The licensed build is not activated.

13) Bulk Backfill

Bulk backfill tools are located at:

WooCommerce → Impact API Connector → Bulk Backfill

A backfill scans paid orders within a selected date range and processes eligible orders in background batches.

Starting a normal backfill

Enter the number of days to look back.
Leave recovery mode unchecked.
Click Start bulk backfill.
Confirm the action.
Refresh the page periodically to view progress.

A normal backfill leaves orders already accepted by Impact alone.

Recovery mode

Enable Recovery mode: retry orders already marked successful only when previous success markers may be unreliable.

This deliberately resubmits orders that the connector normally considers complete. Impact may recognize these as duplicates based on the order ID.

Recovery mode should not be part of routine reconciliation.

Backfill progress

The page can display:

Status
Orders scanned
Orders processed
Conversions accepted
Legacy submissions still pending
Orders not sent
Last update time

Progress does not update live. Refresh the page to see the latest counts.

It is safe to leave or refresh the page after the backfill starts. The job continues through Action Scheduler.

14) Conversion logs

Logs are located at:

WooCommerce → Impact API Connector → Logs

The log records conversion submissions, skipped orders, failures, companion coupon requests, and promo-code synchronization activity.

Searching logs

Enter a WooCommerce order number and click Search.

Each result can include:

Time
Order number
Event
Attribution type
Result level
HTTP response code
Message
Request payload
Impact response body

Select View details to expand the stored payload and response.

Log retention

Choose one of the available retention periods:

One month
Three months
Six months

The default is three months.

Expired logs are removed by a daily scheduled cleanup action.

Clearing all logs

Click Clear all logs to permanently remove the connector’s stored log entries.

The plugin asks for confirmation before continuing. This action cannot be undone unless the database has been backed up separately.

Sensitive information

Standard-mode logs can contain customer, device, location, payment, and product reporting fields.

Only users with the manage_woocommerce capability can access the connector settings and logs, but you should still apply appropriate administrative access controls and retention policies.

HIPAA mode removes the excluded fields before the request is logged.

15) Customer-status classification

The connector sends a CustomerStatus value so Impact can distinguish new customers from existing customers.

For each order, the plugin looks for an earlier paid purchase using:

The WooCommerce customer account ID
The billing email address as a fallback

Only purchases completed before the current order’s conversion time are considered. Later purchases cannot change the classification of an older order during a historical backfill.

The classification result is stored on the order and reused for:

Automatic retries
Manual resends
Automatic reconciliation
Historical backfills

Additional paid statuses configured under Automation are also considered when searching for an earlier qualifying purchase.

16) Privacy, consent, and personal-data tools

Impact API Connector adds suggested disclosure text to the WordPress Privacy Policy Guide.

Review it under:

Settings → Privacy → Policy Guide

Adapt the language to your store’s actual Impact configuration, contracts, consent system, and retention practices before publishing it.

Attribution-cookie consent

Developers can use the sa_iac_allow_attribution_cookie filter to prevent the connector’s first-party cookie from being stored until the site has obtained the required consent.

The filter affects the connector’s cookie only. It does not control cookies created independently by the normal Impact plugin, a tag manager, analytics software, or another integration.

WooCommerce personal-data export

Connector-owned order information is included when WooCommerce exports personal data associated with an order.

Depending on what exists, the export can include:

Impact ClickId
ClickId source
Customer status
Customer-status reason
Stored request payloads
Stored Impact responses

WooCommerce personal-data erasure

When WooCommerce erases personal data from an order, the connector:

Removes its attribution metadata.
Removes its delivery and customer-status metadata.
Deletes connector log entries associated with the order.
Removes pending connector actions for the order.
Records a privacy-erasure marker.
Prevents the order from being submitted again.

The privacy-erasure marker is intentionally retained so future reconciliation does not recreate or resend the erased data.

17) Deactivation and uninstall behavior

Deactivation

Deactivating the plugin stops connector-owned recurring and pending background work.

Saved settings, registry data, order metadata, and logs are not automatically deleted by deactivation.

Remove data on uninstall

The option is located at the bottom of the Logs tab.

When Remove settings and logs when uninstalling is disabled, uninstalling stops scheduled work but preserves the plugin’s stored configuration and database tables.

When the option is enabled, uninstalling also removes:

Plugin settings
Licensing state
Conversion logs
Promo-code registry data
Backfill state
Synchronization status
Plugin database-version options

WooCommerce order metadata may remain with the order because it is part of the order’s historical record. Use WooCommerce’s personal-data erasure tools when connector-owned data must be removed from a particular order.

18) Developer filters

Place customizations in a small site-specific plugin or another version-controlled integration. Do not edit Impact API Connector directly, because plugin updates will replace those changes.

Control attribution-cookie consent

add_filter(
	'sa_iac_allow_attribution_cookie',
	function ( bool $allow, array $click ): bool {
		if ( ! function_exists( 'my_site_has_marketing_consent' ) ) {
			return false;
		}
		return $allow && my_site_has_marketing_consent();
	},
	10,
	2
);

The callback should return true only when the connector may store its first-party attribution cookie.

Change coupon eligibility

add_filter(
	'sa_iac_coupon_is_eligible',
	function ( bool $eligible, string $coupon, WC_Order $order ): bool {
		$excluded_codes = array( 'internal-use', 'staff-discount' );
		return $eligible && ! in_array(
			wc_format_coupon_code( $coupon ),
			$excluded_codes,
			true
		);
	},
	10,
	3
);

This filter runs before the local Impact registry is evaluated.

Customize the conversion payload

add_filter(
	'sa_iac_conversion_payload',
	function ( array $payload, WC_Order $order, bool $hipaa_mode ): array {
		if ( ! $hipaa_mode ) {
			$payload['MyCustomField'] = 'example';
		}
		return $payload;
	},
	10,
	3
);

HIPAA mode applies its strict allowlist after this filter. Custom fields that are not on the HIPAA allowlist will therefore be removed when HIPAA mode is active.

Only add fields supported by the impact.com Conversions API and permitted by your privacy and consent configuration.

Limit the number of line items

add_filter(
	'sa_iac_max_payload_items',
	function ( int $maximum, WC_Order $order ): int {
		return 50;
	},
	10,
	2
);

The plugin bounds the final value between 1 and 250. The default maximum is 100 items.

Allow generated direct-tracking ClickIds

add_filter( 'sa_iac_allow_generated_direct_click_id', '__return_true' );

This allows generated values beginning with ~cglic to qualify as ClickId attribution.

Do not enable this casually. These generated values do not necessarily prove that a commissionable partner click occurred.

19) Troubleshooting

Only the License tab is visible

The licensed build has not been activated.

Open the License tab, enter the purchase key, and activate it. The remaining connector tabs appear only after a valid license is active.

If activation fails:

Confirm the key was entered correctly.
Confirm the license is valid for this product and site count.
Confirm the site can make outbound HTTPS requests to syllable.agency.
Check whether a firewall or security plugin is blocking the request.
Contact Syllable Agency support if the server continues rejecting the key.

Conversion sending will not remain enabled

The minimum Connection settings are incomplete.

Confirm that you entered:

Account SID
Auth Token
Campaign ID
At least one event identifier

After entering the missing value, select Enable conversion sending again and save the settings.

An attributed order is gray

Gray means the connector did not find a trusted ClickId or eligible coupon.

Check:

Whether the customer arrived through a valid Impact attribution link.
Whether the inbound tracking integration was active.
Whether marketing consent prevented the attribution cookie from being created.
Whether the ClickId was saved on the order.
Whether the coupon appears in the current Impact promo-code registry.
Whether the coupon was active and partner-assigned on the order date.
Whether a generated ~cglic identifier was ignored as intended.

Review the private order note and Logs tab for a recorded skip reason.

An order remains yellow

Yellow means the order is awaiting a send or retry.

Check WooCommerce → Status → Scheduled Actions and look for pending or failed actions in the sa-impact-api-connector group.

Also confirm:

WP-Cron or the server cron runner is working.
Action Scheduler is not stalled.
Conversion sending remains enabled.
The license remains active.
The order has payment evidence.
No security plugin is blocking loopback or cron requests.

A delayed checkout check is normally scheduled approximately two minutes after order creation.

An order is red

Open the order and review its private notes, then search for the order number under the Logs tab.

Common categories include:

HTTP 401 or 403: incorrect credentials or insufficient API permissions
HTTP 429: Impact rate limiting
HTTP 5xx: temporary Impact service error
Transport error: DNS, TLS, firewall, or outbound-network failure
Configuration error: required connection settings are missing
Unverified success response: Impact returned a 2xx response without a recognized status value

Transport errors, HTTP 429, and HTTP 5xx responses are retried automatically. Most other 4xx responses require a configuration correction or manual review.

Promo Codes shows “Registry unavailable or stale”

Check:

Account SID
Auth Token
Campaign ID
Promo-code read permission
Whether conversion sending is enabled
Whether the licensed build is active
WooCommerce Scheduled Actions
The synchronization error shown on the page
The latest promo_code_sync entry under Logs

Click Queue sync, wait briefly, and refresh the page.

Coupon filtering fails open while the registry cannot be trusted, so potential coupon attribution is not silently suppressed.

A promo-code sync remains queued

Open WooCommerce → Status → Scheduled Actions and inspect the sa-impact-api-connector group.

If actions are accumulating without running:

Confirm WP-Cron is enabled.
Confirm the site receives traffic or has a server cron runner.
Check for failed Action Scheduler actions.
Check whether the database is writable.
Review PHP and WooCommerce logs for fatal errors.
Confirm another long-running synchronization is not holding the temporary lock.

The synchronization lock expires automatically if an earlier worker stops unexpectedly.

A custom paid status does not trigger a conversion

Enter the exact status slug under Automation → Additional paid statuses.

For example:

intake,review,filling

Do not use the displayed label and do not add a status that can be reached before payment.

After saving, test with a new order or run a bounded backfill covering the affected date.

Automatic backfill does not run

Confirm:

The connector license is active.
Conversion sending is enabled.
Connection settings are complete.
Automatic backfill is enabled.
The selected frequency has elapsed.
Action Scheduler or WP-Cron is operating normally.

Saving the Automation tab removes and recreates the recurring schedule using the current frequency.

Backfill progress appears frozen

Progress does not update live.

Refresh the Bulk Backfill page to retrieve the latest state. It is safe to leave the page after starting a backfill.

If the counters do not change after several scheduled-action cycles, inspect the plugin’s Action Scheduler group for failed or overdue actions.

Failure notification emails do not arrive

Confirm the notification email address under Automation.

If the field is empty, the WordPress administration address is used.

Then test the site’s normal WordPress email delivery. The connector uses wp_mail(), so SMTP, DNS authentication, mail-provider configuration, and spam filtering can all affect delivery.

The failure should still appear in the order notes and Logs tab even if the email is not delivered.

“The link you followed has expired” appears when saving

Reload the settings page and submit the form again. WordPress security tokens can expire when an administrative page has been left open for a long time.

If the problem continues:

Confirm the latest plugin release is installed.
Clear any admin-page cache.
Confirm a security or optimization plugin is not stripping hidden form fields.
Log out of WordPress and back in.
Verify that the site URL, HTTPS configuration, and login cookies are consistent.

Logs contain more customer data than expected

Confirm whether HIPAA mode is enabled under Connection.

Standard mode intentionally records the Impact-supported request payload. HIPAA mode removes customer identifiers, email, IP address, browser information, geography, payment method, and item details before the request and log entry are created.

Changing to HIPAA mode affects future requests. Use Clear all logs or the applicable WooCommerce personal-data erasure process if earlier standard-mode records must be removed.

The Resend to Impact action is missing

Confirm:

You are logged in with permission to manage WooCommerce.
The plugin license is active.
Conversion sending is enabled.
Connection settings are complete.
Connector-owned personal data has not been erased from the order.

The action remains available for an already successful order so an administrator can deliberately force a resend.

20) Recommended launch test

Before relying on the connector in production:

Confirm the normal Impact integration captures a real test affiliate visit.
Place one attributed WooCommerce test order.
Test the checkout type used by the store: classic or Checkout Blocks.
Confirm the order reaches a paid status.
Confirm the Impact column changes to green.
Review the private order note.
Search for the order under Logs.
Confirm the conversion appears in impact.com.
Test one eligible partner coupon.
Confirm the promo-code registry is healthy.
Verify WooCommerce Scheduled Actions are running.
Confirm duplicate browser-side purchase reporting is disabled.
Review the suggested privacy-policy language.
Verify the selected log-retention period.
Test failure-email delivery if notifications are enabled.

A green WordPress status confirms that Impact accepted responsibility for the request. Final attribution and commission treatment should still be confirmed inside the impact.com account.