Audience Activation Settings: Group Activation

Overview

Group Activation features inside Audience Activation let a dealer group coordinate marketing and communications across all stores by sharing shopper events at the group level via the Fullpath CDP. These controls prevent conflicting or redundant sales/service messaging across sister stores and enable group-level marketing decisions that improve the shopper experience.

Navigation

Dashboard > Audience Activation > Product Settings > Group Activation

https://dashboard.fullpath.com/settings/nurture/group-activation
 

Roles & Permissions

• View: Any user with access to the relevant store can view the Group Activation settings page.

• Edit: Requires Edit or Admin level access.

   

Step 1 — Enable Group Synchronization

Group Synchronization is a per-store setting — it must be turned on individually for each store that should listen to shopper events from sister stores in the group. When Enable Group Synchronization is ON for a store, that store can listen to and act on shopper events (purchases, appointments, leads, service ROs) originating from any store in the group.
 

Step 2 — Configure Suppression Windows

Suppression windows control how long sales or service campaigns are paused for a shopper after a group-level event. Each store sets its own values — defaults apply until changed.

Use Cases

• Purchase suppression: If Group Sale = 12 months and Shopper A buys at Dealer A, sales campaigns targeted to Shopper A from Dealer B in the same group will be suppressed for 12 months.
   
• Appointment suppression: If Before Group Service Appointment = 3 days and Shopper B has a service appointment at Dealer C in 3 days, service campaign sends from other group dealers will be suppressed starting 3 days before the appointment.

Troubleshooting

Edits not persisting

• Confirm you have Edit or Admin access.
• Make sure focus leaves the input (click elsewhere or press Tab) — this triggers the automatic save.
• Check for browser pop-ups or modal dialogs that might block focus changes.
• Confirm your browser has JavaScript enabled and no extensions are blocking site scripts.
• Confirm network connectivity — autosave requires a live connection to persist changes.

No visual confirmation after a change

• Look for a transient UI indicator (saved message, checkmark).
• If none appears, re-focus the field afterward to confirm the value persisted.

Best Practices

• Default OFF: Group Synchronization defaults to OFF. Enable it only after confirming Fullpath group ingestion and campaign readiness.
   
• Testing: Validate behavior in a staging/test environment or with a pilot group before enabling across the enterprise.
   
• Communication: Notify dealerships in the group before enabling synchronization to avoid confusion about local campaigns being suppressed.
   

• Granularity: These settings apply per store. Verify with your Fullpath contact if store-level overrides or subgroup settings are needed.

   

Frequently Asked Questions

Group Suppression is a store-level setting that lets a store "listen" for customer touch points (sales, leads, appointments, service ROs) that occur at other stores in the same group. When enabled, the store can pause marketing to customers who have already engaged with any sister store, avoiding duplicate or confusing messages. Each store sets its own pause durations per touchpoint, and those values combine with that store's existing suppression rules to determine whether a customer is paused.

Is this a group setting or a store setting?

It's a store-level setting. Each store must enable Group Suppression individually to start receiving events from sister stores.

Do stores in the same group have to use the same suppression rules?

No. Each store can set different pause durations per touchpoint. If you only enable Group Suppression without changing durations, the stores will have identical defaults, but you can customize each store independently.

Why enable it per store instead of once for the whole group?

Per-store activation gives granular control so each location can define the suppression rules that fit its needs rather than enforcing a single rule across the group.

How do Group Suppression and a store's existing (dealership) suppression rules work together?

The system checks the relevant rule based on where the event occurred: if the customer engaged at the local store, the store's dealership suppression applies; if the customer engaged at a sister store, the store's Group Suppression rule applies. The pause length depends on the event's origin.