{"id":7691,"date":"2021-09-23T09:57:13","date_gmt":"2021-09-23T09:57:13","guid":{"rendered":"https:\/\/docs.campaignsuite.nl\/docs\/gravity-forms\/marketing-cloud\/gutenberg-dynamic-content\/"},"modified":"2022-12-12T11:43:42","modified_gmt":"2022-12-12T11:43:42","slug":"gutenberg-dynamic-content","status":"publish","type":"docs","link":"https:\/\/docs.campaignsuite.nl\/en\/docs\/gravity-forms\/marketing-cloud\/gutenberg-dynamic-content\/","title":{"rendered":"Gutenberg Dynamic Content"},"content":{"rendered":"\n

If a connection with Marketing Cloud has been set up, it is also possible to place Dynamic Content from a Marketing Cloud Page on a page in the website. This is done using a wrapper block called Dynamic Content Wrapper<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This block has different settings in the right column:<\/p>\n\n\n\n

\n
\n

Code type<\/strong>
Dynamic content must always be retrieved based on a campaign code. This value can be sent to Marketing Cloud in several ways:
Page field<\/span>
The code will be retrieved from the Campaign Code field below the block CampaignSuite page settings
Custom<\/span>
The code can be entered manually on the Dynamic Content Wrapper block.

Make campaign code dynamic<\/strong>
It is also possible to extract the code from the URL of the page. Check this option and enter the parameter name from the URL containing the campaign code.<\/p>\n\n\n\n

Content type<\/strong>
There are currently 3 content types available for dynamic content:
Form page<\/span>
This is content that can often be found on a campaign page.
Thank you page<\/span>
This is content that can be displayed on the thank you page after a donation
Next best action<\/span>
This is content that can be used for possible next best actions from a donor.<\/p>\n\n\n\n

Show advanced settings<\/strong>
Under advanced settings it is possible to set a custom endpoint. This endpoint will then overrule the default endpoint in CampaignSuite settings.
It is also possible to choose whether this dynamic block should be rendered Client side or Server side.
Client side<\/span>
By default, the texts are and images loaded into a Dynamic Content Wrapper via javascript. To ensure that the visitor does not see a jump in the content, the entire content of the page will first be hidden. As soon as all dynamic content has been loaded, the page will become visible.
Server side<\/span>
With this option, the server will first make a call to Marketing Cloud to fetch the dynamic content. Then all content will be replaced in the blocks. Eventually the complete page will be loaded.

The main difference between Server and Client side is the fact that with Server side the page ‘keeps loading’ until all content has been replaced. At the Client side, the page has finished loading and the visitor will see a white page for a short time (maximum 1 second). Also, cache plugins can prevent Server side pages from being populated dynamically.<\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

Elements with dynamic content<\/h3>\n\n\n\n

The following Gutenberg blocks within a wrapper can contain dynamic content:<\/p>\n\n\n\n

– Header
– Paragraph
– Image
– Cover image
– Button<\/p>\n\n\n\n

As soon as one of the above fields is placed in a Dynamic Content Wrapper block, the following option appears in the right column:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Check this option to specify that the content of the original block should be replaced with content from Marketing Cloud. If no dynamic content can be retrieved from Marketing Cloud, the original content will remain intact.<\/p>\n","protected":false},"excerpt":{"rendered":"

If a connection with Marketing Cloud has been set up, it is also possible to place Dynamic Content from a Marketing Cloud Page on a page in the website. This is done using a wrapper block called Dynamic Content Wrapper. This block has different settings in the right column: Code typeDynamic content must always be retrieved […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":7565,"menu_order":3,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-7691","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"acf":[],"_links":{"self":[{"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/docs\/7691","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/comments?post=7691"}],"version-history":[{"count":6,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/docs\/7691\/revisions"}],"predecessor-version":[{"id":8068,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/docs\/7691\/revisions\/8068"}],"up":[{"embeddable":true,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/docs\/7565"}],"wp:attachment":[{"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/media?parent=7691"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.campaignsuite.nl\/en\/wp-json\/wp\/v2\/doc_tag?post=7691"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}