{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","settings":"","results":{"codes":[]},"params":[]},"next":{"description":"","pages":[]},"title":"Notification + Card Campaigns","type":"basic","slug":"notification-card-campaigns","excerpt":"Guide how to set up Notification plus Card campaign","body":"***1. Insert Campaign name and select goal***\n\nInsert the campaign name. Select the campaign goal and click continue.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/97a001f-notification_plus_card_campaign.gif\",\n        \"notification plus card campaign.gif\",\n        600,\n        367,\n        \"#f2f3f9\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:embed]\n{\n  \"html\": \"<iframe class=\\\"embedly-embed\\\" src=\\\"//cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0ZuQSXMjKQQ&src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0ZuQSXMjKQQ%3Ffeature%3Doembed&type=text%2Fhtml&key=02466f963b9b4bb8845a05b53d3235d7&schema=youtube\\\" width=\\\"640\\\" height=\\\"480\\\" scrolling=\\\"no\\\" frameborder=\\\"0\\\" allowfullscreen></iframe>\",\n  \"url\": \"https://www.youtube.com/watch?v=0ZuQSXMjKQQ&feature=youtu.be\",\n  \"title\": \"Creating the card for your campaign in Pulsate\",\n  \"favicon\": \"https://s.ytimg.com/yts/img/favicon-vflz7uhzw.ico\"\n}\n[/block]\n***2. Setting Front of the Card***\n\n**Mandatory Font Card Parameters**\nOn the front of the card, the following parameters are mandatory before a campaign can be sent: \n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"Campaign Name\",\n    \"0-1\": \"Every campaign must be given a name in order to proceed. The naming modal becomes active as soon as a user presses Create Campaign and there are two options: \\n- Enter a name for your campaign and press Save and a campaign with that name will be created and you will be able to begin configuring it. \\n- Press Cancel and you will be taken back to the Campaign List screen and no campaign will be created.\",\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"h-2\": \"Description\",\n    \"0-2\": \"On the Front of the Card, one text field (Personal, Headline or Text) must be activated before a campaign can be sent.\",\n    \"1-0\": \"Selected Widget\",\n    \"1-1\": \"At least one widget from the following list must be activated on the front of card:\\n\\n- Personal Message\\n- Image\\n- Headline\\n- Text \\n\\nAny combination of these paramaters can be selected but at least one must be activated on the front of card in order to proceed.\",\n    \"2-0\": \"Call to Action\",\n    \"2-1\": \"At least one of the following Call to Action button destinations must be selected before you can proceed to the next screen: \\n\\n- Card (Back)\\n- Deeplink\\n- URL\"\n  },\n  \"cols\": 2,\n  \"rows\": 3\n}\n[/block]\n**Personal Message**\n\nThe Personal Message widget allows you to send a card to a user as if it is directly from a member of your company. You can choose any Pulsate admin to send the campaign from and these campaigns work best when they are tailored to a very specific segment of users such as High-Value Customers or Lapsed Customers. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": []\n    }\n  ]\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/uI78r60RTjWvSMDP4Ht0_Screen%20Shot%202015-11-30%20at%201.08.41%20p.m..png\",\n        \"Screen Shot 2015-11-30 at 1.08.41 p.m..png\",\n        \"369\",\n        \"298\",\n        \"#48587c\",\n        \"\"\n      ],\n      \"caption\": \"Example of a Personal Message\"\n    }\n  ]\n}\n[/block]\nThe following are a list of all of the parameters that can be added to a Personal Message: \n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"Select Admin\",\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-1\": \"You can choose the admin that you wish to send the card from. You can choose any admin that has been added to your account. To add an admin, please select Settings and then Account Settings. \\n\\nIf you have added a photo for the admin, it will also be send within each card that Personal Message is selected to build up personal rapport with the user who is receiving it. \\n\\nIf you choose to send a card with a Personal Message, it is mandatory to select an admin for the Personal Message.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/9246077-choosing_an_admin.gif\",\n        \"choosing an admin.gif\",\n        600,\n        398,\n        \"#f0f0f7\"\n      ],\n      \"caption\": \"Select Admin\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Personal Message Text\",\n    \"0-1\": \"There is no limit to the amount of text that you can enter for a Personal Message. However, we advise that the optimum length for a personal message is less than 3 lines of text.\",\n    \"1-0\": \"Select a Merge Tag\",\n    \"1-1\": \"Merge tags insert a piece of data that you have sent us about your users. One example is First Name. \\n\\nIf you have supplied us with the [first name of the user](https://pulsate.readme.io/docs/passing-email-address-or-name), we will can programatically insert it into a message to personalise the experience for the user. In situations where we do not have the user's first name, we will not insert anything so those users will not be aware of the merge tag.\\n\\nAny piece of custom data can be used as a merge tag. In the Personal Message section, you can choose to add the label for the custom tag and we will programatically insert the value that was sent to us for that user. Again, if we do not have that custom tag for the user, we will not insert anything. \\n\\nWhen you click Insert to add a Merge tag, you can scroll through the list of available Merge tags or search directly for them. \\n\\nPlease note that if the value of the Merge Tag is quite long (such as a long first name) if will expand the length of this field for the user when it is inserted.\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"caption\": \"Select Merge Tag\",\n      \"image\": [\n        \"https://files.readme.io/GECg2p5jSOa3mSEGecH8_Select%20Merge%20Tag%202.gif\",\n        \"Select Merge Tag 2.gif\",\n        \"471\",\n        \"601\",\n        \"#925830\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n**Image**\n\nGreat imagery can really improve your card and entice users to really take notice of it and take that next important stop of clicking on one of the Call To Action buttons to find out more. \n\nThis is a list of the parameters that you need to be aware of when you decide to add an image to your card:\n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Image Sizes\",\n    \"0-1\": \"Images must be be a minimum width of 500px\",\n    \"1-0\": \"Image File Size\",\n    \"1-1\": \"The image file must not be more than 700kb\",\n    \"2-0\": \"Supported Image Types\",\n    \"2-1\": \"The following image types are supported by Pulsate: \\n\\nJPEG\\nPNG\\nGIF\",\n    \"3-0\": \"Drag and Drop Image Builder\",\n    \"3-1\": \"To Add an Image you should enable and open the Image Widget by clicking anywhere on the widget and then either drag and drop an image or press Click Here to manually locate the image on your machine. \\n\\nIf you wish to Remove an image that you have uploaded, press *Remove*.\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/d6bq0oFvR1qqC2IU4vQR_Add%20Image.gif\",\n        \"Add Image.gif\",\n        \"1495\",\n        \"503\",\n        \"#3a587e\",\n        \"\"\n      ],\n      \"caption\": \"Add/ Remove Image\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Crop Image\",\n    \"0-1\": \"Pulsate also allows you to crop any image that you upload. To crop an image, select *Crop* and a new modal will appear. \\n\\nYou can then drag the cropping cropper around the image until you are happy with the new dimensions. When the image is satisfactorily cropped, press the *Crop* button. \\n\\nIf you wish to edit the image dimensions or return to the original dimensions, you can follow the same steps. \\n\\nPlease note that you cannot crop an image and\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"caption\": \"Cropping an Image\",\n      \"image\": [\n        \"https://files.readme.io/T7hmMvzAQCyAm4b5OqW8_Crop.gif\",\n        \"Crop.gif\",\n        \"1495\",\n        \"747\",\n        \"\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n**Headline**\n\nThe Headline widget is great for quickly getting a message across to users with bold text. It is much more direct than a Personal Message but also less tailored to individual users and/ or segments. \n\nHeadlines should be short and snappy and only a few words long to make it as striking as possible. You can also add merge tags to the Headline widget by pressing the *Insert* button when you are in the widget. See Personal Message for more information on Merge Tags. \n[block:image]\n{\n  \"images\": [\n    {\n      \"caption\": \"Headline Example\",\n      \"image\": [\n        \"https://files.readme.io/IAiWuYfFTrqdhhmCnhgM_Screen%20Shot%202015-11-30%20at%203.31.02%20p.m..png\",\n        \"Screen Shot 2015-11-30 at 3.31.02 p.m..png\",\n        \"381\",\n        \"432\",\n        \"#785a47\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n**Text**\n\nThe text widget can be used as a standalone widget to outline the message that you are trying to deliver with the camapign card. However, it can also be used in addition to the other widgets (Personal Message, Image and Headline) to add more information to the content within those widgets. It is a great way to add extra information about the campaign you are sending and the copy entered should be short, snappy and informative for the end user. \n\n\nUse the text widget to explain why somebody should be interested in the campaign that you are sending and to offer additional background information for the user. You can also insert merge tags into the text widget to include the user's name or some other piece of custom data. See Personal Message above for more information on merge tags.\n\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/ygunQUI4TIk8vh9d7f5v_Text%20Widget.gif\",\n        \"Text Widget.gif\",\n        \"1219\",\n        \"703\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Text Example\"\n    }\n  ]\n}\n[/block]\n**Call to Action**\n\nThe front of card call to action widget is mandatory for all campaigns. It allows you to specify a destination for your card and also to specify whether or not you want to allow users to reply to that campaign. Finally, the call to action widget also allows you to setup an In-App event to record which users click on the call to action event that you specify. \n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/7mt0wmPaRzWYxCYIZvQy_Screen%20Shot%202015-12-13%20at%2010.12.03%20a.m..png\",\n        \"Screen Shot 2015-12-13 at 10.12.03 a.m..png\",\n        \"468\",\n        \"476\",\n        \"#9f6c64\",\n        \"\"\n      ],\n      \"caption\": \"Call to o Action widget\"\n    }\n  ]\n}\n[/block]\n**Call to Action Parameters**\n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Campaign Reply\",\n    \"0-1\": \"This checkbox allows you to specify whether or not users can reply to this card. By default this option is checked so user's will be able to reply to the campaign and a Reply button will be added to the bottom of the card along with the other call to action button. \\n\\nWhen a user clicks on that reply button, they will be able to compose a reply to that card either with feedback about the campaign or any questions that they have about it. When a user replies to a card, their message will be available for you in the Messages section of the CMS and the campaign name will be listed so that you know which campaign they are replying to. For more information on Pulsate's messaging functionality, please see [Starting a Conversation](doc:step-3-starting-a-conversation) \\n\\nIf you do not wish to allow a user to reply to this campaign, uncheck this box and the Reply button will be removed from the campaign card.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/SBnHYWEHSGSo97sAJmc4_Reply.gif\",\n        \"Reply.gif\",\n        \"1235\",\n        \"695\",\n        \"#af562d\",\n        \"\"\n      ],\n      \"caption\": \"Reply Checkbox\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Button Text\",\n    \"0-1\": \"Every campaign that has a card must have a destination for that card. The destination can be the back of the card, somewhere else within the app or a URL outside the app (more info on these options below). \\n\\nThe Button Text field allows you to specify what text should appear on the Call to Action button. The default text is 'View More' but you can enter any text that you want into this field. \\n\\nHowever, please note that if you have allowed user's to reply to their campaign, any text that you enter into this field that is over 15 characters will truncate. If you have not enabled campaign reply, any text over 33 characters will be truncated.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/VDcfQf0AQgKX2KMYO315_Button%20Text.gif\",\n        \"Button Text.gif\",\n        \"1235\",\n        \"695\",\n        \"#a34f2f\",\n        \"\"\n      ],\n      \"caption\": \"Button Text\"\n    }\n  ]\n}\n[/block]\nOptional setup Card Back, Deeplink or URL\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Card (Back)\",\n    \"0-1\": \"If you select the Card (Back) option, you will be able to setup the destination of the card to an ancillary card that can provide more information and images for the user. \\n\\nThis option is useful if you have a lot of information that you want to send to the user that will not fit on the front of card alone or if you wish to add a table of information of such as store opening hours. \\n\\nWhen you select the Card (Back) option, another step will be added to the navigation bar at the bottom of the screen and you will be able to design the back of card when you press the Next button. \\n\\nCard (Back) is selected by default in the Call to Action section.\",\n    \"1-0\": \"Deeplink\",\n    \"1-1\": \"Instead of bringing users to an ancillary card, you can bring them to another location within your app that is outside of the Pulsate feed. You will need to first setup a deeplink for the view within your app that you want to route users to and you can find out more information about setting up deeplinks for [iOS](doc:supporting-deep-links) or [Android](doc:supporting-deep-links-1) by following those links. \\n\\nWhen you have setup deeplinks as per the instructions above, you will be able to select them in a dropdown when you select the deeplink call to action option.\",\n    \"2-0\": \"URL\",\n    \"2-1\": \"It allows binging user to an URL\"\n  },\n  \"cols\": 2,\n  \"rows\": 3\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0ESTyGcFQsGX6LP6Qeud_Deeplink.gif\",\n        \"Deeplink.gif\",\n        \"468\",\n        \"656\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Selecting a deeplink\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"URL\",\n    \"0-1\": \"You can also route the user directly to a web page. When you select the URL call to action option, you will be able to enter a web page and if users click on the call to action button, that web page will open on their mobile devices. \\n\\nPlease note that you have to enter the full URL address so if you wanted to send users to the Pulsate website you should enter *http://www.pulsatehq.com* as the URL and not just *www.pulsatehq.com*\\n\\nFinally, it is important to check that any website that you are directing users to is optimised for mobile devices so that your users have the best possible experience.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/YkvqeDmQxCERt68lOEfw_URL.gif\",\n        \"URL.gif\",\n        \"468\",\n        \"656\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Adding a URL\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"In-App Events\",\n    \"0-1\": \"An In-App Event is any action that the user takes when they are within your app. Outside of the Pulsate Feed, you can setup In-App Events to record actions that users take. You can setup a campaign to be delivered when the user carries out that action or simply use the information for analytical purposes. \\n\\nFor information on setting up In-App Events outside of the Pulsate Feed, please consult our guides for [iOS](doc:creating-custom-events) and [Android](doc:setting-custom-events).\\n\\nWithin the Pulsate Feed, you can setup an in-app event to record when a user clicks on one of the call to action buttons that were specified above. This allows you to track the conversion rate for your campaign and to find out how many users have clicked on each call to action button. \\n\\nTo add an In-App Event to a call to action item, click on *In-App Event* and a text field will open. You can use this text field to enter the name of the in-app event. When you are naming these in-app events it is best to come up with a set naming protocol or else you will end up with lots of in-app events called did_click_buttonX or something along those lines. \\n\\nIt is useful to include the name of the campaign in the title of the In App Event so that you can quickly reference what campaign the event was recorded from.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/upyX9eoBS4F8boaaJtqw_In%20App%20Event.gif\",\n        \"In App Event.gif\",\n        \"468\",\n        \"656\",\n        \"#49a6e2\",\n        \"\"\n      ],\n      \"caption\": \"Adding an In App Event\"\n    }\n  ]\n}\n[/block]\n***3. Setting Back of the card***\n\nThe back of card option allows you to bring users to another campaign card with more information and imagery. The back of card has more space that the front of card so it enables you to include much more detail for the user.\n\nJust like on the front of the card, you must select at least one widget. You can also select multiple widgets at the same time and reorder those widgets into whichever order you wish. Unlike the front of card, the call to action widget is not mandatory on the back of card so it can be switched off if you wish. \n\nIf you have included a personal message on the front of the card, this message will be displayed at the top of the back of card. Likewise, if you allowed users to reply to the campaign, a reply icon will be added to the top navbar at the back of the card.\n\n\n**Back of Card Parameters**\n\n\n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Image\",\n    \"0-1\": \"Much like on the front of the card, you can add an image to the back of card as well. However, as you have the full screen to play with on the back of the card, the image can be a bit longer. \\n\\nImages on the back of card must also be a minnimum width of 300px and a maximum size of 1MB. \\n\\nYou can also crop the image on the back of card. Please refer to the front of card image documentation for specific instructions on cropping an image.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/MveZieUoTF2iI6oyLGsP_Back%20Image%20Crop2.gif\",\n        \"Back Image Crop2.gif\",\n        \"1259\",\n        \"784\",\n        \"#4d7da5\",\n        \"\"\n      ],\n      \"caption\": \"Adding and Cropping Image\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Headline\",\n    \"0-1\": \"Much like on the front of the card, the purpose of the Headline is to immediately grab the user's attention and let them know what the campaign is about. \\n\\nHeadline is an optional widget once at least one other widget has been selected. \\n\\nMerge tags can also be added to the headline field if you wish to personalise the message and/ or programatically insert some custom data into the headline.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/VXI21cAFT8S0YtTLERMz_Back%20Headline.gif\",\n        \"Back Headline.gif\",\n        \"1222\",\n        \"595\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Adding a Headline\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Text\",\n    \"0-1\": \"The function of the text widget on the back of the card is the same as its function on the front of the card. It is a great way to add complimentary  detail to an image or headline. There is more room on the back of the card than the front so there is also an opportunity to add more text. However, for optimal results, the text entered should be short and snappy and to the point.\\n\\nMerge tags can also be added to the text field if you wish to personalise the message and/ or programatically insert some custom data into the headline.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0kKhLdQRadJRcHTg3BBw_Back%20text.gif\",\n        \"Back text.gif\",\n        \"1222\",\n        \"595\",\n        \"#9f503e\",\n        \"\"\n      ],\n      \"caption\": \"Adding Text\"\n    }\n  ]\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Table\",\n    \"0-1\": \"The table widget is a great way to provide structured information for the user such as store opening hours or prices. When the widget is selected you can enter a heading for the table and a series of rows under the View and Label headings. \\n\\nTo add a new row, press the *Add* button and to delete a row press the *minus* button.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/3wA8kwO6TXfjBc7LOLKU_Table.gif\",\n        \"Table.gif\",\n        \"1222\",\n        \"704\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Adding a Table\"\n    }\n  ]\n}\n[/block]\n**Call to Action**\n\nFor the back of card, you have the option to select call to action buttons. If you do not wish to include a call to action on that back of the card, you can turn the widget off and the user will  not be able to go any further. \n\nHowever, if you do choose to enable the call to action widget on the back of the card, you will be able to choose one or two call to action buttons. To select these buttons click the checkboxes when the widget is open. Once the number of buttons has been selected, you can specify the text and destination of each button. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/gJl99UnbRa6DYsZdXK0j_Back%20CTA.gif\",\n        \"Back CTA.gif\",\n        \"1222\",\n        \"831\",\n        \"\",\n        \"\"\n      ],\n      \"caption\": \"Call to Action\"\n    }\n  ]\n}\n[/block]\nIf you decide to turn the Call to Action widget on, there are a number of options on the back or card:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Deeplink\",\n    \"0-1\": \"Just like on the front of card if you select Deeplink, you can route users to another location within your app that is outside of the Pulsate feed. You will need to first setup a deeplink for the view within your app that you want to route users to and you can find out more information about setting up deeplinks for [iOS](doc:supporting-deep-links) or [Android](doc:supporting-deep-links-1) by following those links. \\n\\nWhen you have setup deeplinks as per the instructions above, you will be able to select them in a dropdown when you select the deeplink call to action option.\",\n    \"1-0\": \"URL\",\n    \"1-1\": \"You can also route the user directly to a web page. When you select the URL call to action option, you will be able to enter a web page and if users click on the call to action button, that web page will open on their mobile devices. \\n\\nPlease note that you have to enter the full URL address so if you wanted to send users to the Pulsate website you should enter *http://www.pulsatehq.com* as the URL and not just *www.pulsatehq.com*\\n\\nFinally, it is important to check that any website that you are directing users to is optimised for mobile devices so that your users have the best possible experience.\",\n    \"2-0\": \"Dismiss\",\n    \"2-1\": \"On the back of card you can also select an option to dismiss the current view. When this is selected, it will route users back to the front of the card if they press it.\",\n    \"3-0\": \"In-App Events\",\n    \"3-1\": \"On the back of card, you can setup an in-app event for each button that you enable in the call to action widget. This allows you to track the conversion rate for your campaign and to find out how many users have clicked on each call to action button. \\n\\nTo add an In-App Event to one or both of the back or card buttons item, click on *In-App Event* within the CTA widget for each button and a text field will open. You can use this text field to enter the name of the in-app event. When you are naming these in-app events it is best to come up with a set naming protocol or else you will end up with lots of in-app events called did_click_buttonX or something along those lines. \\n\\nIt is useful to include the name of the campaign in the title of the In App Event so that you can quickly reference what campaign the event was recorded from.\\n\\nFor information on setting up In-App Events outside of the Pulsate Feed, please consult our guides for [iOS](doc:creating-custom-events) and [Android](doc:setting-custom-events).\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n***4. Select Notification Type***\n\nPulsate allows choosing four options of how the user will be notified.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Type\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Push Notification\",\n    \"1-0\": \"In-App Notification\",\n    \"2-0\": \"Appears in Feed\",\n    \"3-0\": \"User Receives SMS\",\n    \"1-1\": \"This notification will appear the next time the user is in the app. You can select size small or full screen. [More about In-App notifications here](https://pulsate.readme.io/v4.1/docs/inapp-notification-campaigns)\",\n    \"2-1\": \"The user will not be notified but the new card will appear when they are in their feed.\",\n    \"3-1\": \"Delivers notification to your user's mobile phone as an SMS. [More about SMS notifications here](https://pulsate.readme.io/v4.1/docs/sms-campaigns)\",\n    \"0-1\": \"A push notification is a message that pops up on a mobile device. [More about push notifications here](https://pulsate.readme.io/v4.1/docs/push-notification-campaigns)\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://readmetemppulsate.s3-eu-west-1.amazonaws.com/card-delivery-options.png\",\n        \"Card Delivery Options.gif\",\n        \"1222\",\n        \"831\",\n        \"\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n***5. Select Targeting***\n\nWhen you have created your notification and chosen a destination for it, press the Next button to bring you into the Targeting section. Here you will be able to choose which groups of your users get your campaign. This is the audience for your notification and as much as possible it should be chosen based on the group of users that you believe will be most interested in this campaign based on their previous transaction history, current proximity to a physical location and/ or in-app actions that the users will take within your app. \n\nIn the Targeting section you can choose from the following parameters: \n\n- Segments \n- Beacons\n- Geofences\n- In-App Events\n\nWhen you choose any of these parameters, they will be displayed on the left-hand side of the screen in the Targeting simulator with an estimate of how many users the campaign will be sent to.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/ec17696-Screen_Shot_2016-07-27_at_13.49.56.png\",\n        \"Screen Shot 2016-07-27 at 13.49.56.png\",\n        1466,\n        693,\n        \"#f3f9f9\"\n      ]\n    }\n  ]\n}\n[/block]\nWith Pulsate you can choose to target as many Segments, Beacons, Geofences and In App Events as you want. However, you should be trying to send each campaign to as well targeted a group of users as possible to ensure the highest open rates. You can send a campaign to multiple Segments of users and/ or send it to users who enter a Beacon, Geofence or carry out a specific in app action. Don't worry though, users will only receive the campaign once by default no matter how many of these parameters that they meet unless you specify otherwise whilst sending the campaign. \n\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Pro Tip\",\n  \"body\": \"Use the search functionality when you are looking for a Segment, Beacon, Geofence or In-App Event to quickly find the one that you are looking for.\"\n}\n[/block]\nYou can also set up a Control Group in the Targeting section. For more information on Control Groups and how to set them up, please go [here](doc:control-groups).\n\n***6. Select Delivery***\n\nNow that you have set up your notification and chosen what users should receive it, the final step is to define when and how often users should receive your campaign. There are different scheduling options depending on whether you have chosen to send a campaign to a Segment or chosen to send it to any combination of Segments, Beacons, Geofences or In-App Events. The reason for the difference is that if you are sending a campaign to only a segment, you may want to just send the campaign to users already in the segment. \n\nHowever, if you decide to send the campaign to users who enter or exit a beacon or geofence region or carry out an In-App Event (and possibly are also in a segment), you are relying on those users being in that location or carrying out that event in the future so you cannot just send it to users already in that segment. \n\n##Segment Only Campaigns\nAs mentioned above, if you send a campaign exclusively with a segment you will be given a choice whether to send the campaign only to users who are already in the segment or users in the segment combined with users who may enter the segment at some point in the future whilst the campaign is live. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/eaa8992-Screen_Shot_2016-07-27_at_14.09.58.png\",\n        \"Screen Shot 2016-07-27 at 14.09.58.png\",\n        1053,\n        446,\n        \"#f3fafa\"\n      ]\n    }\n  ]\n}\n[/block]\n###People in the segment now\n\nIf you choose to send the campaign to only users who are currently in the segment, it will be sent to every user that is in the segment when the campaign is sent and the campaign will then end. However you can still choose whether the campaign should be sent now or at some point in the future. \n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/7afc40b-Screen_Shot_2016-07-27_at_14.17.15.png\",\n        \"Screen Shot 2016-07-27 at 14.17.15.png\",\n        921,\n        731,\n        \"#eef3f3\"\n      ]\n    }\n  ]\n}\n[/block]\nThere is no option for an end date when you are sending a campaign to People in the segment now because the campaign will be ended as soon as it is sent to all users in that segment.\n\n\n### People who enter the segment in the future\n\nThere are a number of different options if you want to send a campaign to users who enter the segment in the future too. \n\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2ba4dc8-Screen_Shot_2016-07-27_at_14.52.13.png\",\n        \"Screen Shot 2016-07-27 at 14.52.13.png\",\n        1036,\n        1072,\n        \"#f2f9f9\"\n      ]\n    }\n  ]\n}\n[/block]\nThe first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter the segment but you only want to send it once even if the user leaves and re-enters the segment at some point in the future. \n\nConversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment. If you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that.\n\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/47958b7-Screenshot_2020-07-16_at_16.43.26.png\",\n        \"Screenshot 2020-07-16 at 16.43.26.png\",\n        1914,\n        1254,\n        \"#f0f6f6\"\n      ]\n    }\n  ]\n}\n[/block]\nThe final choice to make is to decide when the campaign should be scheduled. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish.\n\n\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/18ba9ad-Screen_Shot_2016-07-29_at_10.19.28.png\",\n        \"Screen Shot 2016-07-29 at 10.19.28.png\",\n        841,\n        433,\n        \"#4f88b7\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Pro Tip\",\n  \"body\": \"If you would like to sett your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox.\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2954a96-Screen_Shot_2016-07-29_at_10.24.48.png\",\n        \"Screen Shot 2016-07-29 at 10.24.48.png\",\n        701,\n        281,\n        \"#deddd9\"\n      ]\n    }\n  ]\n}\n[/block]\n#Delivery for Other Campaigns\n\nIf you wish to send a campaign based on the user entering or exiting a beacon or geofence or carrying out an in app event in your app and/ or combining those targeting types with a segment, you have slightly different targeting options. As users will be carrying out these actions in the future, you can only target people who will receive the campaign in the future. \n\nThe first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter a physical location but you only want to send it once even if the user leaves and re-enters the beacon or geofence region at some point in the future. \n\nConversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment.\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1c6c75b-Screen_Shot_2016-07-29_at_10.31.19.png\",\n        \"Screen Shot 2016-07-29 at 10.31.19.png\",\n        973,\n        825,\n        \"#f2f6f6\"\n      ]\n    }\n  ]\n}\n[/block]\nIf you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that.\n\nThe final choice to make is to decide when the campaign should be sent now or scheduled for some point in the future. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish.\n\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/00facc0-Screen_Shot_2016-07-29_at_10.19.31.png\",\n        \"Screen Shot 2016-07-29 at 10.19.31.png\",\n        927,\n        547,\n        \"#5189b9\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Be Careful\",\n  \"body\": \"Please ensure that you add an end date if you want this card to be removed from the feed at some point in the future. It will not be possible to change this after the campaign is sent.\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"If you would like to sett your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox.\",\n  \"title\": \"Pro Tip\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1ebdcaf-Screen_Shot_2016-07-29_at_10.24.48.png\",\n        \"Screen Shot 2016-07-29 at 10.24.48.png\",\n        701,\n        281,\n        \"#deddd9\"\n      ]\n    }\n  ]\n}\n[/block]\n***7. Review and activate the campaign***\n\nCongratulations, your campaign is almost ready to be sent. Before you send it, Pulsate enable you to review everything that you have set up one last time so that you can make sure that everything is perfect. \n\nThe first thing you will notice on the Review page is the key parameters for this campaign which are what app the campaign is being sent for, the estimated reach of the campaign and when the campaign will be sent. \n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/8c1d16d-Screen_Shot_2016-07-29_at_10.41.42.png\",\n        \"Screen Shot 2016-07-29 at 10.41.42.png\",\n        1593,\n        154,\n        \"#4a5c7e\"\n      ]\n    }\n  ]\n}\n[/block]\nAs you scroll down through the rest of the review page, you will be able to check the other details that you have set for that campaign including the Notification, Targeting and Delivery Options. If you see anything that you would like to change, you can quickly jump to that section by pressing the back button located at the bottom of the page.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://readmetemppulsate.s3-eu-west-1.amazonaws.com/Review+and+back.gif\",\n        \"Review Campaign.gif\",\n        1590,\n        1207,\n        \"#3d4054\"\n      ]\n    }\n  ]\n}\n[/block]\nOnce you are happy with all of the parameters that you have set for the campaign, you are ready to send it. To send the campaign press the Activate Campaign button at the bottom of the screen. You will be asked to confirm that you wish to send the campaign. If you are ready to send, press Activate Campaign and your campaign will be activated and sent when you have specified.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://readmetemppulsate.s3-eu-west-1.amazonaws.com/submit+the+campaign.gif\",\n        \"submit campaign.gif\",\n        1559,\n        651,\n        \"#f3fbfb\"\n      ]\n    }\n  ]\n}\n[/block]","updates":[],"order":2,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"5f58d9e781143a0025a4f41d","createdAt":"2020-09-09T13:34:31.879Z","user":"54aa7f3f9bb00c0b00cb899b","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Campaigns","slug":"campaigns-v2","order":3,"from_sync":false,"reference":false,"_id":"5f58c9ac42683f019c302ac3","createdAt":"2020-09-08T13:29:05.710Z","version":"5f58c9ac42683f019c302b1f","project":"54aa7f773b56130b0056c86e","__v":0},"version":{"version":"4.1","version_clean":"4.1.0","codename":"For Marketers","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["5f58c9ac42683f019c302ab5","5f58c9ac42683f019c302ab6","576a656c6f15260e001f893b","576a656c6f15260e001f893c","576a656c6f15260e001f893d","5f58c9ac42683f019c302ab7","5f58c9ac42683f019c302ab8","5f58c9ac42683f019c302ab9","5f58c9ac42683f019c302aba","5f0dcc9ac6cae402ffef097e","5f58c9ac42683f019c302abb","5f58c9ac42683f019c302abc","5f58c9ac42683f019c302abd","5f58c9ac42683f019c302abe","5f58c9ac42683f019c302abf","5f58c9ac42683f019c302ac0","5f58c9ac42683f019c302ac1","5f3d2cc209dce706808729bd","5f58c9ac42683f019c302ac2","5f58c9ac42683f019c302ac3","5f58cab1ab8ee10056fe22a7","5f58ebe66e59f30073a5b81a","5f69c35f16803d0065b24502","5f69c36f95979600656d1977"],"_id":"5f58c9ac42683f019c302b1f","createdAt":"2016-06-22T10:16:12.661Z","__v":4,"project":"54aa7f773b56130b0056c86e","releaseDate":"2016-06-22T10:16:12.661Z","forked_from":"576a656c6f15260e001f8938"},"project":"54aa7f773b56130b0056c86e","__v":0,"parentDoc":null}

Notification + Card Campaigns

Guide how to set up Notification plus Card campaign

***1. Insert Campaign name and select goal*** Insert the campaign name. Select the campaign goal and click continue. [block:image] { "images": [ { "image": [ "https://files.readme.io/97a001f-notification_plus_card_campaign.gif", "notification plus card campaign.gif", 600, 367, "#f2f3f9" ] } ] } [/block] [block:embed] { "html": "<iframe class=\"embedly-embed\" src=\"//cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0ZuQSXMjKQQ&src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0ZuQSXMjKQQ%3Ffeature%3Doembed&type=text%2Fhtml&key=02466f963b9b4bb8845a05b53d3235d7&schema=youtube\" width=\"640\" height=\"480\" scrolling=\"no\" frameborder=\"0\" allowfullscreen></iframe>", "url": "https://www.youtube.com/watch?v=0ZuQSXMjKQQ&feature=youtu.be", "title": "Creating the card for your campaign in Pulsate", "favicon": "https://s.ytimg.com/yts/img/favicon-vflz7uhzw.ico" } [/block] ***2. Setting Front of the Card*** **Mandatory Font Card Parameters** On the front of the card, the following parameters are mandatory before a campaign can be sent: [block:parameters] { "data": { "0-0": "Campaign Name", "0-1": "Every campaign must be given a name in order to proceed. The naming modal becomes active as soon as a user presses Create Campaign and there are two options: \n- Enter a name for your campaign and press Save and a campaign with that name will be created and you will be able to begin configuring it. \n- Press Cancel and you will be taken back to the Campaign List screen and no campaign will be created.", "h-0": "Name", "h-1": "Description", "h-2": "Description", "0-2": "On the Front of the Card, one text field (Personal, Headline or Text) must be activated before a campaign can be sent.", "1-0": "Selected Widget", "1-1": "At least one widget from the following list must be activated on the front of card:\n\n- Personal Message\n- Image\n- Headline\n- Text \n\nAny combination of these paramaters can be selected but at least one must be activated on the front of card in order to proceed.", "2-0": "Call to Action", "2-1": "At least one of the following Call to Action button destinations must be selected before you can proceed to the next screen: \n\n- Card (Back)\n- Deeplink\n- URL" }, "cols": 2, "rows": 3 } [/block] **Personal Message** The Personal Message widget allows you to send a card to a user as if it is directly from a member of your company. You can choose any Pulsate admin to send the campaign from and these campaigns work best when they are tailored to a very specific segment of users such as High-Value Customers or Lapsed Customers. [block:image] { "images": [ { "image": [] } ] } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/uI78r60RTjWvSMDP4Ht0_Screen%20Shot%202015-11-30%20at%201.08.41%20p.m..png", "Screen Shot 2015-11-30 at 1.08.41 p.m..png", "369", "298", "#48587c", "" ], "caption": "Example of a Personal Message" } ] } [/block] The following are a list of all of the parameters that can be added to a Personal Message: [block:parameters] { "data": { "0-0": "Select Admin", "h-0": "Name", "h-1": "Description", "0-1": "You can choose the admin that you wish to send the card from. You can choose any admin that has been added to your account. To add an admin, please select Settings and then Account Settings. \n\nIf you have added a photo for the admin, it will also be send within each card that Personal Message is selected to build up personal rapport with the user who is receiving it. \n\nIf you choose to send a card with a Personal Message, it is mandatory to select an admin for the Personal Message." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/9246077-choosing_an_admin.gif", "choosing an admin.gif", 600, 398, "#f0f0f7" ], "caption": "Select Admin" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Personal Message Text", "0-1": "There is no limit to the amount of text that you can enter for a Personal Message. However, we advise that the optimum length for a personal message is less than 3 lines of text.", "1-0": "Select a Merge Tag", "1-1": "Merge tags insert a piece of data that you have sent us about your users. One example is First Name. \n\nIf you have supplied us with the [first name of the user](https://pulsate.readme.io/docs/passing-email-address-or-name), we will can programatically insert it into a message to personalise the experience for the user. In situations where we do not have the user's first name, we will not insert anything so those users will not be aware of the merge tag.\n\nAny piece of custom data can be used as a merge tag. In the Personal Message section, you can choose to add the label for the custom tag and we will programatically insert the value that was sent to us for that user. Again, if we do not have that custom tag for the user, we will not insert anything. \n\nWhen you click Insert to add a Merge tag, you can scroll through the list of available Merge tags or search directly for them. \n\nPlease note that if the value of the Merge Tag is quite long (such as a long first name) if will expand the length of this field for the user when it is inserted." }, "cols": 2, "rows": 2 } [/block] [block:image] { "images": [ { "caption": "Select Merge Tag", "image": [ "https://files.readme.io/GECg2p5jSOa3mSEGecH8_Select%20Merge%20Tag%202.gif", "Select Merge Tag 2.gif", "471", "601", "#925830", "" ] } ] } [/block] **Image** Great imagery can really improve your card and entice users to really take notice of it and take that next important stop of clicking on one of the Call To Action buttons to find out more. This is a list of the parameters that you need to be aware of when you decide to add an image to your card: [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Image Sizes", "0-1": "Images must be be a minimum width of 500px", "1-0": "Image File Size", "1-1": "The image file must not be more than 700kb", "2-0": "Supported Image Types", "2-1": "The following image types are supported by Pulsate: \n\nJPEG\nPNG\nGIF", "3-0": "Drag and Drop Image Builder", "3-1": "To Add an Image you should enable and open the Image Widget by clicking anywhere on the widget and then either drag and drop an image or press Click Here to manually locate the image on your machine. \n\nIf you wish to Remove an image that you have uploaded, press *Remove*." }, "cols": 2, "rows": 4 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/d6bq0oFvR1qqC2IU4vQR_Add%20Image.gif", "Add Image.gif", "1495", "503", "#3a587e", "" ], "caption": "Add/ Remove Image" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Crop Image", "0-1": "Pulsate also allows you to crop any image that you upload. To crop an image, select *Crop* and a new modal will appear. \n\nYou can then drag the cropping cropper around the image until you are happy with the new dimensions. When the image is satisfactorily cropped, press the *Crop* button. \n\nIf you wish to edit the image dimensions or return to the original dimensions, you can follow the same steps. \n\nPlease note that you cannot crop an image and" }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "caption": "Cropping an Image", "image": [ "https://files.readme.io/T7hmMvzAQCyAm4b5OqW8_Crop.gif", "Crop.gif", "1495", "747", "", "" ] } ] } [/block] **Headline** The Headline widget is great for quickly getting a message across to users with bold text. It is much more direct than a Personal Message but also less tailored to individual users and/ or segments. Headlines should be short and snappy and only a few words long to make it as striking as possible. You can also add merge tags to the Headline widget by pressing the *Insert* button when you are in the widget. See Personal Message for more information on Merge Tags. [block:image] { "images": [ { "caption": "Headline Example", "image": [ "https://files.readme.io/IAiWuYfFTrqdhhmCnhgM_Screen%20Shot%202015-11-30%20at%203.31.02%20p.m..png", "Screen Shot 2015-11-30 at 3.31.02 p.m..png", "381", "432", "#785a47", "" ] } ] } [/block] **Text** The text widget can be used as a standalone widget to outline the message that you are trying to deliver with the camapign card. However, it can also be used in addition to the other widgets (Personal Message, Image and Headline) to add more information to the content within those widgets. It is a great way to add extra information about the campaign you are sending and the copy entered should be short, snappy and informative for the end user. Use the text widget to explain why somebody should be interested in the campaign that you are sending and to offer additional background information for the user. You can also insert merge tags into the text widget to include the user's name or some other piece of custom data. See Personal Message above for more information on merge tags. [block:image] { "images": [ { "image": [ "https://files.readme.io/ygunQUI4TIk8vh9d7f5v_Text%20Widget.gif", "Text Widget.gif", "1219", "703", "", "" ], "caption": "Text Example" } ] } [/block] **Call to Action** The front of card call to action widget is mandatory for all campaigns. It allows you to specify a destination for your card and also to specify whether or not you want to allow users to reply to that campaign. Finally, the call to action widget also allows you to setup an In-App event to record which users click on the call to action event that you specify. [block:image] { "images": [ { "image": [ "https://files.readme.io/7mt0wmPaRzWYxCYIZvQy_Screen%20Shot%202015-12-13%20at%2010.12.03%20a.m..png", "Screen Shot 2015-12-13 at 10.12.03 a.m..png", "468", "476", "#9f6c64", "" ], "caption": "Call to o Action widget" } ] } [/block] **Call to Action Parameters** [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Campaign Reply", "0-1": "This checkbox allows you to specify whether or not users can reply to this card. By default this option is checked so user's will be able to reply to the campaign and a Reply button will be added to the bottom of the card along with the other call to action button. \n\nWhen a user clicks on that reply button, they will be able to compose a reply to that card either with feedback about the campaign or any questions that they have about it. When a user replies to a card, their message will be available for you in the Messages section of the CMS and the campaign name will be listed so that you know which campaign they are replying to. For more information on Pulsate's messaging functionality, please see [Starting a Conversation](doc:step-3-starting-a-conversation) \n\nIf you do not wish to allow a user to reply to this campaign, uncheck this box and the Reply button will be removed from the campaign card." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/SBnHYWEHSGSo97sAJmc4_Reply.gif", "Reply.gif", "1235", "695", "#af562d", "" ], "caption": "Reply Checkbox" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Button Text", "0-1": "Every campaign that has a card must have a destination for that card. The destination can be the back of the card, somewhere else within the app or a URL outside the app (more info on these options below). \n\nThe Button Text field allows you to specify what text should appear on the Call to Action button. The default text is 'View More' but you can enter any text that you want into this field. \n\nHowever, please note that if you have allowed user's to reply to their campaign, any text that you enter into this field that is over 15 characters will truncate. If you have not enabled campaign reply, any text over 33 characters will be truncated." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/VDcfQf0AQgKX2KMYO315_Button%20Text.gif", "Button Text.gif", "1235", "695", "#a34f2f", "" ], "caption": "Button Text" } ] } [/block] Optional setup Card Back, Deeplink or URL [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Card (Back)", "0-1": "If you select the Card (Back) option, you will be able to setup the destination of the card to an ancillary card that can provide more information and images for the user. \n\nThis option is useful if you have a lot of information that you want to send to the user that will not fit on the front of card alone or if you wish to add a table of information of such as store opening hours. \n\nWhen you select the Card (Back) option, another step will be added to the navigation bar at the bottom of the screen and you will be able to design the back of card when you press the Next button. \n\nCard (Back) is selected by default in the Call to Action section.", "1-0": "Deeplink", "1-1": "Instead of bringing users to an ancillary card, you can bring them to another location within your app that is outside of the Pulsate feed. You will need to first setup a deeplink for the view within your app that you want to route users to and you can find out more information about setting up deeplinks for [iOS](doc:supporting-deep-links) or [Android](doc:supporting-deep-links-1) by following those links. \n\nWhen you have setup deeplinks as per the instructions above, you will be able to select them in a dropdown when you select the deeplink call to action option.", "2-0": "URL", "2-1": "It allows binging user to an URL" }, "cols": 2, "rows": 3 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/0ESTyGcFQsGX6LP6Qeud_Deeplink.gif", "Deeplink.gif", "468", "656", "", "" ], "caption": "Selecting a deeplink" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "URL", "0-1": "You can also route the user directly to a web page. When you select the URL call to action option, you will be able to enter a web page and if users click on the call to action button, that web page will open on their mobile devices. \n\nPlease note that you have to enter the full URL address so if you wanted to send users to the Pulsate website you should enter *http://www.pulsatehq.com* as the URL and not just *www.pulsatehq.com*\n\nFinally, it is important to check that any website that you are directing users to is optimised for mobile devices so that your users have the best possible experience." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/YkvqeDmQxCERt68lOEfw_URL.gif", "URL.gif", "468", "656", "", "" ], "caption": "Adding a URL" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "In-App Events", "0-1": "An In-App Event is any action that the user takes when they are within your app. Outside of the Pulsate Feed, you can setup In-App Events to record actions that users take. You can setup a campaign to be delivered when the user carries out that action or simply use the information for analytical purposes. \n\nFor information on setting up In-App Events outside of the Pulsate Feed, please consult our guides for [iOS](doc:creating-custom-events) and [Android](doc:setting-custom-events).\n\nWithin the Pulsate Feed, you can setup an in-app event to record when a user clicks on one of the call to action buttons that were specified above. This allows you to track the conversion rate for your campaign and to find out how many users have clicked on each call to action button. \n\nTo add an In-App Event to a call to action item, click on *In-App Event* and a text field will open. You can use this text field to enter the name of the in-app event. When you are naming these in-app events it is best to come up with a set naming protocol or else you will end up with lots of in-app events called did_click_buttonX or something along those lines. \n\nIt is useful to include the name of the campaign in the title of the In App Event so that you can quickly reference what campaign the event was recorded from." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/upyX9eoBS4F8boaaJtqw_In%20App%20Event.gif", "In App Event.gif", "468", "656", "#49a6e2", "" ], "caption": "Adding an In App Event" } ] } [/block] ***3. Setting Back of the card*** The back of card option allows you to bring users to another campaign card with more information and imagery. The back of card has more space that the front of card so it enables you to include much more detail for the user. Just like on the front of the card, you must select at least one widget. You can also select multiple widgets at the same time and reorder those widgets into whichever order you wish. Unlike the front of card, the call to action widget is not mandatory on the back of card so it can be switched off if you wish. If you have included a personal message on the front of the card, this message will be displayed at the top of the back of card. Likewise, if you allowed users to reply to the campaign, a reply icon will be added to the top navbar at the back of the card. **Back of Card Parameters** [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Image", "0-1": "Much like on the front of the card, you can add an image to the back of card as well. However, as you have the full screen to play with on the back of the card, the image can be a bit longer. \n\nImages on the back of card must also be a minnimum width of 300px and a maximum size of 1MB. \n\nYou can also crop the image on the back of card. Please refer to the front of card image documentation for specific instructions on cropping an image." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/MveZieUoTF2iI6oyLGsP_Back%20Image%20Crop2.gif", "Back Image Crop2.gif", "1259", "784", "#4d7da5", "" ], "caption": "Adding and Cropping Image" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Headline", "0-1": "Much like on the front of the card, the purpose of the Headline is to immediately grab the user's attention and let them know what the campaign is about. \n\nHeadline is an optional widget once at least one other widget has been selected. \n\nMerge tags can also be added to the headline field if you wish to personalise the message and/ or programatically insert some custom data into the headline." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/VXI21cAFT8S0YtTLERMz_Back%20Headline.gif", "Back Headline.gif", "1222", "595", "", "" ], "caption": "Adding a Headline" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Text", "0-1": "The function of the text widget on the back of the card is the same as its function on the front of the card. It is a great way to add complimentary detail to an image or headline. There is more room on the back of the card than the front so there is also an opportunity to add more text. However, for optimal results, the text entered should be short and snappy and to the point.\n\nMerge tags can also be added to the text field if you wish to personalise the message and/ or programatically insert some custom data into the headline." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/0kKhLdQRadJRcHTg3BBw_Back%20text.gif", "Back text.gif", "1222", "595", "#9f503e", "" ], "caption": "Adding Text" } ] } [/block] [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Table", "0-1": "The table widget is a great way to provide structured information for the user such as store opening hours or prices. When the widget is selected you can enter a heading for the table and a series of rows under the View and Label headings. \n\nTo add a new row, press the *Add* button and to delete a row press the *minus* button." }, "cols": 2, "rows": 1 } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/3wA8kwO6TXfjBc7LOLKU_Table.gif", "Table.gif", "1222", "704", "", "" ], "caption": "Adding a Table" } ] } [/block] **Call to Action** For the back of card, you have the option to select call to action buttons. If you do not wish to include a call to action on that back of the card, you can turn the widget off and the user will not be able to go any further. However, if you do choose to enable the call to action widget on the back of the card, you will be able to choose one or two call to action buttons. To select these buttons click the checkboxes when the widget is open. Once the number of buttons has been selected, you can specify the text and destination of each button. [block:image] { "images": [ { "image": [ "https://files.readme.io/gJl99UnbRa6DYsZdXK0j_Back%20CTA.gif", "Back CTA.gif", "1222", "831", "", "" ], "caption": "Call to Action" } ] } [/block] If you decide to turn the Call to Action widget on, there are a number of options on the back or card: [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "Deeplink", "0-1": "Just like on the front of card if you select Deeplink, you can route users to another location within your app that is outside of the Pulsate feed. You will need to first setup a deeplink for the view within your app that you want to route users to and you can find out more information about setting up deeplinks for [iOS](doc:supporting-deep-links) or [Android](doc:supporting-deep-links-1) by following those links. \n\nWhen you have setup deeplinks as per the instructions above, you will be able to select them in a dropdown when you select the deeplink call to action option.", "1-0": "URL", "1-1": "You can also route the user directly to a web page. When you select the URL call to action option, you will be able to enter a web page and if users click on the call to action button, that web page will open on their mobile devices. \n\nPlease note that you have to enter the full URL address so if you wanted to send users to the Pulsate website you should enter *http://www.pulsatehq.com* as the URL and not just *www.pulsatehq.com*\n\nFinally, it is important to check that any website that you are directing users to is optimised for mobile devices so that your users have the best possible experience.", "2-0": "Dismiss", "2-1": "On the back of card you can also select an option to dismiss the current view. When this is selected, it will route users back to the front of the card if they press it.", "3-0": "In-App Events", "3-1": "On the back of card, you can setup an in-app event for each button that you enable in the call to action widget. This allows you to track the conversion rate for your campaign and to find out how many users have clicked on each call to action button. \n\nTo add an In-App Event to one or both of the back or card buttons item, click on *In-App Event* within the CTA widget for each button and a text field will open. You can use this text field to enter the name of the in-app event. When you are naming these in-app events it is best to come up with a set naming protocol or else you will end up with lots of in-app events called did_click_buttonX or something along those lines. \n\nIt is useful to include the name of the campaign in the title of the In App Event so that you can quickly reference what campaign the event was recorded from.\n\nFor information on setting up In-App Events outside of the Pulsate Feed, please consult our guides for [iOS](doc:creating-custom-events) and [Android](doc:setting-custom-events)." }, "cols": 2, "rows": 4 } [/block] ***4. Select Notification Type*** Pulsate allows choosing four options of how the user will be notified. [block:parameters] { "data": { "h-0": "Type", "h-1": "Description", "0-0": "Push Notification", "1-0": "In-App Notification", "2-0": "Appears in Feed", "3-0": "User Receives SMS", "1-1": "This notification will appear the next time the user is in the app. You can select size small or full screen. [More about In-App notifications here](https://pulsate.readme.io/v4.1/docs/inapp-notification-campaigns)", "2-1": "The user will not be notified but the new card will appear when they are in their feed.", "3-1": "Delivers notification to your user's mobile phone as an SMS. [More about SMS notifications here](https://pulsate.readme.io/v4.1/docs/sms-campaigns)", "0-1": "A push notification is a message that pops up on a mobile device. [More about push notifications here](https://pulsate.readme.io/v4.1/docs/push-notification-campaigns)" }, "cols": 2, "rows": 4 } [/block] [block:image] { "images": [ { "image": [ "https://readmetemppulsate.s3-eu-west-1.amazonaws.com/card-delivery-options.png", "Card Delivery Options.gif", "1222", "831", "", "" ] } ] } [/block] ***5. Select Targeting*** When you have created your notification and chosen a destination for it, press the Next button to bring you into the Targeting section. Here you will be able to choose which groups of your users get your campaign. This is the audience for your notification and as much as possible it should be chosen based on the group of users that you believe will be most interested in this campaign based on their previous transaction history, current proximity to a physical location and/ or in-app actions that the users will take within your app. In the Targeting section you can choose from the following parameters: - Segments - Beacons - Geofences - In-App Events When you choose any of these parameters, they will be displayed on the left-hand side of the screen in the Targeting simulator with an estimate of how many users the campaign will be sent to. [block:image] { "images": [ { "image": [ "https://files.readme.io/ec17696-Screen_Shot_2016-07-27_at_13.49.56.png", "Screen Shot 2016-07-27 at 13.49.56.png", 1466, 693, "#f3f9f9" ] } ] } [/block] With Pulsate you can choose to target as many Segments, Beacons, Geofences and In App Events as you want. However, you should be trying to send each campaign to as well targeted a group of users as possible to ensure the highest open rates. You can send a campaign to multiple Segments of users and/ or send it to users who enter a Beacon, Geofence or carry out a specific in app action. Don't worry though, users will only receive the campaign once by default no matter how many of these parameters that they meet unless you specify otherwise whilst sending the campaign. [block:callout] { "type": "info", "title": "Pro Tip", "body": "Use the search functionality when you are looking for a Segment, Beacon, Geofence or In-App Event to quickly find the one that you are looking for." } [/block] You can also set up a Control Group in the Targeting section. For more information on Control Groups and how to set them up, please go [here](doc:control-groups). ***6. Select Delivery*** Now that you have set up your notification and chosen what users should receive it, the final step is to define when and how often users should receive your campaign. There are different scheduling options depending on whether you have chosen to send a campaign to a Segment or chosen to send it to any combination of Segments, Beacons, Geofences or In-App Events. The reason for the difference is that if you are sending a campaign to only a segment, you may want to just send the campaign to users already in the segment. However, if you decide to send the campaign to users who enter or exit a beacon or geofence region or carry out an In-App Event (and possibly are also in a segment), you are relying on those users being in that location or carrying out that event in the future so you cannot just send it to users already in that segment. ##Segment Only Campaigns As mentioned above, if you send a campaign exclusively with a segment you will be given a choice whether to send the campaign only to users who are already in the segment or users in the segment combined with users who may enter the segment at some point in the future whilst the campaign is live. [block:image] { "images": [ { "image": [ "https://files.readme.io/eaa8992-Screen_Shot_2016-07-27_at_14.09.58.png", "Screen Shot 2016-07-27 at 14.09.58.png", 1053, 446, "#f3fafa" ] } ] } [/block] ###People in the segment now If you choose to send the campaign to only users who are currently in the segment, it will be sent to every user that is in the segment when the campaign is sent and the campaign will then end. However you can still choose whether the campaign should be sent now or at some point in the future. [block:image] { "images": [ { "image": [ "https://files.readme.io/7afc40b-Screen_Shot_2016-07-27_at_14.17.15.png", "Screen Shot 2016-07-27 at 14.17.15.png", 921, 731, "#eef3f3" ] } ] } [/block] There is no option for an end date when you are sending a campaign to People in the segment now because the campaign will be ended as soon as it is sent to all users in that segment. ### People who enter the segment in the future There are a number of different options if you want to send a campaign to users who enter the segment in the future too. [block:image] { "images": [ { "image": [ "https://files.readme.io/2ba4dc8-Screen_Shot_2016-07-27_at_14.52.13.png", "Screen Shot 2016-07-27 at 14.52.13.png", 1036, 1072, "#f2f9f9" ] } ] } [/block] The first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter the segment but you only want to send it once even if the user leaves and re-enters the segment at some point in the future. Conversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment. If you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that. [block:image] { "images": [ { "image": [ "https://files.readme.io/47958b7-Screenshot_2020-07-16_at_16.43.26.png", "Screenshot 2020-07-16 at 16.43.26.png", 1914, 1254, "#f0f6f6" ] } ] } [/block] The final choice to make is to decide when the campaign should be scheduled. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish. [block:image] { "images": [ { "image": [ "https://files.readme.io/18ba9ad-Screen_Shot_2016-07-29_at_10.19.28.png", "Screen Shot 2016-07-29 at 10.19.28.png", 841, 433, "#4f88b7" ] } ] } [/block] [block:callout] { "type": "info", "title": "Pro Tip", "body": "If you would like to sett your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox." } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/2954a96-Screen_Shot_2016-07-29_at_10.24.48.png", "Screen Shot 2016-07-29 at 10.24.48.png", 701, 281, "#deddd9" ] } ] } [/block] #Delivery for Other Campaigns If you wish to send a campaign based on the user entering or exiting a beacon or geofence or carrying out an in app event in your app and/ or combining those targeting types with a segment, you have slightly different targeting options. As users will be carrying out these actions in the future, you can only target people who will receive the campaign in the future. The first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter a physical location but you only want to send it once even if the user leaves and re-enters the beacon or geofence region at some point in the future. Conversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment. [block:image] { "images": [ { "image": [ "https://files.readme.io/1c6c75b-Screen_Shot_2016-07-29_at_10.31.19.png", "Screen Shot 2016-07-29 at 10.31.19.png", 973, 825, "#f2f6f6" ] } ] } [/block] If you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that. The final choice to make is to decide when the campaign should be sent now or scheduled for some point in the future. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish. [block:image] { "images": [ { "image": [ "https://files.readme.io/00facc0-Screen_Shot_2016-07-29_at_10.19.31.png", "Screen Shot 2016-07-29 at 10.19.31.png", 927, 547, "#5189b9" ] } ] } [/block] [block:callout] { "type": "warning", "title": "Be Careful", "body": "Please ensure that you add an end date if you want this card to be removed from the feed at some point in the future. It will not be possible to change this after the campaign is sent." } [/block] [block:callout] { "type": "info", "body": "If you would like to sett your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox.", "title": "Pro Tip" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/1ebdcaf-Screen_Shot_2016-07-29_at_10.24.48.png", "Screen Shot 2016-07-29 at 10.24.48.png", 701, 281, "#deddd9" ] } ] } [/block] ***7. Review and activate the campaign*** Congratulations, your campaign is almost ready to be sent. Before you send it, Pulsate enable you to review everything that you have set up one last time so that you can make sure that everything is perfect. The first thing you will notice on the Review page is the key parameters for this campaign which are what app the campaign is being sent for, the estimated reach of the campaign and when the campaign will be sent. [block:image] { "images": [ { "image": [ "https://files.readme.io/8c1d16d-Screen_Shot_2016-07-29_at_10.41.42.png", "Screen Shot 2016-07-29 at 10.41.42.png", 1593, 154, "#4a5c7e" ] } ] } [/block] As you scroll down through the rest of the review page, you will be able to check the other details that you have set for that campaign including the Notification, Targeting and Delivery Options. If you see anything that you would like to change, you can quickly jump to that section by pressing the back button located at the bottom of the page. [block:image] { "images": [ { "image": [ "https://readmetemppulsate.s3-eu-west-1.amazonaws.com/Review+and+back.gif", "Review Campaign.gif", 1590, 1207, "#3d4054" ] } ] } [/block] Once you are happy with all of the parameters that you have set for the campaign, you are ready to send it. To send the campaign press the Activate Campaign button at the bottom of the screen. You will be asked to confirm that you wish to send the campaign. If you are ready to send, press Activate Campaign and your campaign will be activated and sent when you have specified. [block:image] { "images": [ { "image": [ "https://readmetemppulsate.s3-eu-west-1.amazonaws.com/submit+the+campaign.gif", "submit campaign.gif", 1559, 651, "#f3fbfb" ] } ] } [/block]