OE / AM sync
The docs say:
Contacts Synchronization is performed by the sync service. The service loops over the active sync targets that have a URL for the contacts sync server and for each server sync segments and new / changed / deleted contacts.
Does this happen regardless of whether a publish sync target is assigned?
Background
I have a STAGE and LIVE env separated by a firewall - our ASP.NET site deployed to both uses Audience Manager as the repository for ASP.NET membership.
STAGE has the profilesync.aspx and OE API / CD options to use the STAGE_submgmt table so that the staging site can function properly - but how do I get the contacts into this table?
If I create a new sync target to point to profilesync.aspx on STAGE, I cannot assign posts to it because they are using the LIVE sync target. It is important?
Or, it's just faster to do a manual backup / restore of the LIVE paging table and not sync with STAGE at all.
source to share
Sync targets will be used even if they are not assigned for publishing (unless you disable them by checking the box in the edit screen). However, no contacts will be synced in this case - because there is no address book to sync. Other elements - such as segments and tracking information - will continue to be synced.
I'm a little confused about your setup. Why are publications on your staging system pointing to sync goals for your live system? This means that the contacts in your staging environment are synchronized with your website. Since you created separate databases for it, I am assuming that this is not what you want.
In this case, I highly recommend deleting the "Live" sync targets in your staging environment and adding only those in your staging database. Otherwise, your staging environment is actively interacting with your living environment.
Edit . Remember, contacts are not content. They are not published but synchronized. Most people do not manage contacts themselves, leaving them to the site users to maintain their profile. This way you also have the option of not having separate databases for staging. It all depends on how you are going to use it. If you need separate databases, you will need separate instances of Content Manager for them.
source to share