After you complete your historical data loads, you can start thinking about how to continuously send data into Bluecore to keep your audiences, campaigns, coupons, and more up-to-date.

Most data can be updated through a near real-time (NRT) update, managed feed, or both, and your Bluecore team can help you decide which options work best for you.

To avoid sending large batch files, just send the unique identifier that is being created or updated and the data that has changed.

Depending on how your data is stored, it may be beneficial for you to integrate to both the NRT and batch delivery options.

For example, if Bluecore is not your sole email service provider (ESP) and you are collecting Email Eligibility updates from other sources, we recommend capturing Bluecore updates through the NRT option, and using the batch feed from the other ESPs.

Most of the data ingestion points have options for both batch or NRT, but understanding how you want to use that data may help in deciding which options are best for you.

For example, if you want to use audiences based on purchases, using the NRT option will keep your audiences more up-to-date.

You can review additional considerations to help decide the best options for you.

The Email Eligibility data ingestion captures whether the customer's Email Eligibility status is known, opt-in, or unsubscribed, which informs which customers can receive campaigns.

Customer Purchases collects data from all channels and sources, such as website, in store, mobile app, call centers, or anywhere else your customers purchase.

Customer Behavioral Events encompass all events customers do in your website and/or mobile app.

This can only be captured using the Bluecore Website integration.

The Product Catalog ingestion delivers updates about products, such as inventory.

The Customer Profile ingestion delivers updates about customers, such as email address, name, or birthday month.

You can include custom attributes in your ingestion as long as it’s used for segmentation or personalization.

The Transparent ID captures the events that create a Customer Profile, such as collecting a customer's email address when they register an account.

Identify customers by using first-party cookies, which recognizes a customer by addressable identifiers, such as email address or phone number, and matches them to previously collected behavior.

Identify customers using second- or third-party data.

Update customer eligibility for your marketing SMS/MMS campaigns.

Sending your content sync data into Bluecore creates consistency across your website and emails by pulling content from predetermined areas of your website to use in campaigns.

If you use Content Sync, you only need to update your website and that data will be automatically synced into Bluecore as customers view the content on your website.

For example, if you have a blog where you feature top performing categories, the Content Sync data ingestion captures the latest blog details.

There are two ways to process a Right to be Forgotten request: manually submitting a request in the Bluecore platform, or through a managed feed via SFTP in Files.com.

If you plan to submit batches of more than 100 emails or phone numbers at a time, you can submit files via a managed feed.

You can manually submit Right to be Forgotten requests if you have smaller batch sizes.

One-time coupons can be added to a coupon code bank via a manual file import within Bluecore.