Skip to content

Personalized campaigns pre-requirements

Leaflet

  • the leaflet should satisfy the Solver AI Suite data model defined and communicated in the initial phase of integration
  • all items should have prices (regular price, discount price) that are communicated through the personalized campaign
  • all items should have correct and exact names (case sensitivity is active)
  • file export containing the items that are going to be communicated in the campaign
  • in case the campaign is using a failover to SMS, the leaflet should contain the correct items names for SMS. (excluding Latin letters, , , Š, , Ž, etc, since they can affect the size of the message, whereas the goal is to fit into a single message)

Note: if any part of the leaflet is changed, Things Solver is not responsible for the feature stability and can take from one sprint to more, depends on how big are changes.

Images

  • the item images should be exported to a predefined location (public storage)
  • the image format can be png or jpg
  • all images should be names in format {item_id}.{format}
  • the agreed format is predefined in PoC/Integration phase and should be respected in all campaigns that follow
  • all images should be transparent following product lines
  • in order to have better visualization, the developer’s advice is to keep the original product ratio in images, not to fix it to equal height-width ratio

Template

  • the template is a minimum of 300x300 px, if not should have the same HxW
  • the template cannot have any part of the visualization fixed, should that part be changed from campaign to campaign (i.e. date, price, etc.)
  • the template is tested and agreed upon in the PoC/Integration phase
  • in case there is a need to change the template in later phases, it is labeled as a change request and should be reported in a timely manner, in order to handle it through the standard product development process

Text of message

  • The text should be defined in the input body, including placeholders for maximum 3 products
  • Available placeholders:
    • first-product-name
    • second-product-name
    • third-product-name
    • first-product-price
    • second-product-price
    • third-product-price
    • first-product-points
    • second-product-points
    • third-product-points
  • in case a failover option is used, the SMS content must be entered, following the same rules as the Viber content (including placeholders)

Button text

  • the button text is defined in the input field

Button URL

  • a button URL is defined in the input field, where the campaign creator is responsible for the availability and accessibility of the URL entered
  • if the client doesn't have the possibility to use public storage for their resources, Things Solver can offer a storage, where in that case, the client is needed to upload the resources and assure that they are available and accessible

Target audience

  • in order to create a target audience which will receive a personalized Viber message, Audience lab component within Customer Studio is used
  • the campaign creator can control additional filters predefined in the Audience lab
  • the campaign creator doesn't control which customer is targeted by which product, if personalized template is used (because the content is dynamically populated based on given placeholders and recommendations extracted on a customer level)

Note: the product doesn't currently support the option to upload a CSV or XLSX file with the list of customers and a list of products, and thus automatically create a personalized campaign

Campaign schedule time

  • the campaign execution date and time are defined in Campaigning studio in the process of campaign creation
  • al the materials required ( item images, leaflet, items with regular and discount prices, ... ) should be prepared and uploaded at least 24 hours prior the campaign start time is defined
Back to top