Keep members in sync nightly

Once Fonteva, Nimble AMS or Protech is connected and mapped, Keep in sync reads it again every night. New members come in, changed terms are updated, people whose membership lapsed lose the Member tag, and the event registrations your AMS keeps are added to each person’s activity. The read never changes anything in your AMS.

Why use it

A member list is out of date the day after you import it. Keeping it in sync means the Member tag, the member engagement snapshot and every list you hand to Marketing, Sessions, Learning or Awards reflect who is a member today, without anyone importing a file again.

Turn it on

An admin turns on Keep in sync for the AMS on Connections. The nightly read runs as the admin who turned it on. If that person leaves your organization, the read stops; turn it on again as someone else. Turn it off at any time: the people already brought in stay.

If you don’t see Keep in sync, it isn’t turned on for your organization. Ask us to turn it on.

What each night’s read does

1. Reads every member. A full read through your field mapping, up to 50,000 members.
2. Brings members in. New people are added to People. For people already there, the membership term is updated only when their member type, status or renewal date changed. Current members are tagged Member. Their companies are found or added under People › Groups, and each person is linked to their AMS record so the next read matches them.
3. Untags lapsed members. The Member tag comes off people the read now says are lapsed. They stay in People.
4. Adds registrations. The registrations your AMS keeps since the last successful read become registered and checked-in activity on each person. The first read goes back 12 months. A registration is never counted twice.
5. Writes back, if you turned it on. Only the Sessionboard objects you switched on, and only rows that changed. See Write engagement back to your AMS.

Who loses the Member tag

The nightly read removes the Member tag only from people this connection tagged. Someone a team member tagged Member by hand keeps the tag, whatever the AMS says.

Caution

The mass-lapse guard. If a read returns fewer than half the members the previous read found, nobody is untagged that night, and the run says why. A drop that large usually means the mapping changed or the run-as user lost access, not that half your members lapsed. Nobody is untagged either when a read is cut short. Check the field mapping and the run-as user’s access; the next good read untags as usual.

The last run

Each connection keeps what its last read did: how many members it found, how many were current and lapsed, how many people were added, updated, linked and untagged, how many registrations it read and added, and what it wrote back. When the guard held the untagging, the reason is there too.

Note

The nightly read is the source of truth. To have a lapse or a new membership show up within minutes instead of the next morning, add membership updates as they happen on top. People brought in count as active contacts only once you reach them: see Active contacts.

Related

• Map your AMS fields
• Get membership updates as they happen
• Bring in attendees and members