The dreaded ERR_HTTP2_PROTOCOL_ERROR error. Just search for this one and you’ll see there is little consistency in fixes, and a lot of confusion. All development environments started throwing this error, but only on sign in. Why only there? A bad security measure was the culprit.

I had to create a new local development environment for Sitecore XP today, which will be our last before moving to Sitecore AI. Now, I know I need these environments for at least a couple of years, and the installation certificates will expire before then. I loath changing all the thumbprints and dealing with new certs, so I plan to change the expiration date during installation.

I’m getting feedback from people out there that the Send Batch Upload and Merge module is saving them a lot of time, and that’s great! There is one thing I missed in the API’s behaviour, and you may have missed it to, and that’s the fact that some result data is being sent as an error.

It's that time of year again! No, not Thanksgiving, Black Friday, holiday preparations, etc. I'm talking about Sitecore MVP application time!

In my last post I covered sending data to a Send email list, and my last comment was about making sure Authors don't have to jump through hoops to get its Guid. In this post I'll share making this selection a custom field in Content Editor. 

I recently built a helper method for our Send gateway which adds or resubscribe users to specified lists. I reported a bug since resubscribing Users kept reverting to unsubscribed. I'll cover the workaround and the explanation from Send for this behaviour. 

Ok, that's it! We're in the final piece of this four-part series for the Send to CDP Sync module. In this episode, we will cover the API calls used for deploying the batch file, monitoring its progress and securing the local cache which was covered in the last post.

So far, we've covered the Send to CDP module's introduction, getting data from Send and preparing a list of guests for upload. Since there's a hard limit of 50mb per upload I wanted to use a local cache so only changes are sent on each iteration. We'll go over that in this post.

In my first post I introduced you to the Sitecore to CDP module, which will create a structured extension with all Send email lists and if the Guest subscribed to them. In this post I'll walk through the process of getting all data out of chosen Send lists so they can be sent to CDP as a batch file.

What if you wanted to instantly see all Send email lists your CDP Guests are subscribed to? This module will collect information from Send and populate CDP with what they've signed up for. It also maintains the last updated timestamps for each list preference and deploys the changes in batch files. Uploads are minimal by using a local cache, and the preferences are structured in a single extension.