Campaign Members

The Create or Update a Spiro Campaign Member action adds the triggering contact to a Marketing Campaign. Paminga campaigns sync to Spiro as Spiro Lists, so when the campaign has a linked Spiro List, the contact is added to that list as well. Additions flow into Spiro. Removals don't.

How It Works

1. Pick the Marketing Campaign in the action config.
2. When the action fires, the contact becomes a member of that campaign in Paminga.
3. If the campaign has a linked Spiro List, Paminga adds the contact to it. A campaign created moments ago may not have its Spiro List yet, so Paminga retries for several minutes while the list is created.

Contacts who are already members are updated rather than duplicated, and a contact already on the list isn't added twice. The action is safe to trigger repeatedly.

The Contact Must Already Be in Spiro

This action doesn't create Spiro Contacts. It adds a contact to the Spiro List only if that contact has already synced to Spiro as a Contact. If the contact is still on its way (because a Create/Update a Contact in CRM action fired at the same moment, for example), Paminga retries for several minutes before giving up. A contact that never reaches Spiro stays a member of the Paminga campaign but isn't added to the Spiro List.

To give new members the best chance of reaching Spiro, put a Create/Update a Contact in CRM action in the same place as this one so the contact is on its way to Spiro first.

Membership Syncs Back From Spiro

Removing a contact from the campaign in Paminga doesn't remove them from the Spiro List. Changes made in Spiro flow back to Paminga instead.

Each down sync from Spiro, both a full sync and the hourly differential sync that runs once your first full sync has completed, re-reads every linked Spiro List's full membership. That's because Spiro records no timestamps on list membership, so there's no "what changed" to ask for. Contacts added to a list in Spiro become members of the matching Marketing Campaign. Contacts removed from a list in Spiro are removed from the campaign, as long as Campaigns is checked in your sync settings along with Campaign Members.

Member Field Values

You can set values for Campaign Member custom fields as part of the action. Existing members have their field values updated per your selections, which makes this a clean way to stamp members with source, status, or scoring data as they arrive.

These values live on the Paminga campaign member. Spiro Lists have no member fields of their own, so they aren't sent to Spiro.