--- title: How to create a Campaign with CSV slug: how-to-create-a-campaign-with-csv 'og:title': How to create a Campaign | Fyno Documentation 'og:description': >- This document describes how to create a campaign from scratch using SMS channel and CSV file upload image: type: url value: 'https://images.fyno.io/brand/fyno-doc-preview.png' --- In this tutorial, we will: 1. Create a Fyno notification template (for SMS) 2. Create a Notification Event to link the template and the integration. 3. Create and trigger the campaign. 4. View campaign logs and analytics. ## Prerequisites To create a Campaign, you will first need to have a few things in place: - A service provider integration in Fyno’s platform - A pre-approved SMS template created in DLT platform along with DLT Template ID - A CSV file with the user base to whom you would be triggering the campaign. If there are variables in your template which require a different value for every user, you may place these values in the CSV file as well. Once we have these in place, we are all set to go with campaigns! ## Creating a SMS Template To create a SMS template, from the left nav, select **Templates→Fyno** You will land on Templates Listing Page. Click ‘**+Create**’ and select ‘SMS’ as channel and provide a name for your Template and click ‘Create’ **Template Id** - Enter your approved DLT template Id. **SMS Content** - Copy & Paste the SMS content from your DLT platform in this section. Once you have added the content, you will see the the following fields **Unicode** - Enable this, if the SMS content or placeholder values contain Unicode or non-English characters. If the message isn't marked as unicode and either the content or placeholder values contain unicode characters, it might not be delivered correctly. SMS providers may charge you more for unicode messages.![](file:d47598c0-284c-4c4b-b56a-f19807ee631e) **Additional Configuration** ![](file:926b204a-6420-40c4-8480-2a2a3c63001e) **Placeholders** - Below the “Channels” section on the left, you can find placeholders. Placeholders are denoted by {{}}. You can add the parameters of Placeholders by clicking on it, which opens up a pop-up window where you can add them. You can use our Handlebar functions with your placeholders for operations such as Date formatting, number formatting, arithmetic operations etc. You can refer this doc for Handlebars.![](file:adbee41c-d421-45a4-8602-788af33ce2f9)![](file:1e9c0dcb-3102-411f-b030-87f605ad76c3) **Preview** - Once you have done all the steps, you will see the Preview on the Right Hand Side. All the placeholders you defined (like name, loan_amount etc) will be replaced with sample values added. **Run Test** - To make sure, the SMS template works as expected, you can click ‘Run Test’. A pop up opens up. Enter the mobile no where you want to send the SMS and select the Integration through which you want to send the SMS.![](file:b0bea962-a2b0-49f0-b8cd-9e47c026dd82) Save & Go Live - Clicking ‘Save’ will create a Test version of the template. Clicking ‘Go Live’ will create a Live version of the template. ## Creating a Notification Event Notification Event = Template + Service Providers (integrations) To create a new Notification Event, from the left nav, select Notification Events. Click ‘**+Create**’ and provide a name for your Notification Event. You can use the same name as the Template. Select ‘Type’ from one of the options - OTP, Transactional and Marketing. Click ‘Create’ The first step to building a “**Notification Event**” with Fyno is to select a template that you have already created in the “**Templates**” section.![](file:ed298c8a-6d26-47d3-9442-2aba3b75818f) On clicking on the drop-down, you will see the entire list of templates created. Select one to proceed. On selecting a template, you will even be able to see the preview of the template on the right hand side.![](file:9d0fd135-3e93-423d-ae2e-c39f1863005d) If you wish to edit the selected template click on the ‘EDIT TEMPLATE’ button right above the template preview on the right hand side. On clicking the drop down under Routes/Provider, select ‘**Single Channel Provider or Route**’. Under ‘Send SMS using’, select the Integration name.![](file:fb896ed9-8c4d-4668-8f62-9f56bbd0b483) **Preview** Once you have done all the steps, you will see the Preview on the Right Hand Side. **Test** To make sure, the notification event works as expected, you can click ‘Test’ on top right corner next to ‘Go Live’ button. A pop up opens up. Enter the mobile no where you want to send the SMS and enter sample values for the placeholders defined in the template![](file:135d8f3c-074a-4717-a265-6792c5bb54f2) Click ‘**Test Notification**’ to test if the notification event works as expected. **Logs** - Logs will show you the status of the notification **Code** - This will give you the cURL command for both Test and Live versions. This is the cURL command you need if you trigger the notification from your backend. **Save & Go Live -** Clicking ‘Save’ will create a Test version of the Notification Event. Clicking ‘Go Live’ will create a Live version of the Notification Event. ## Creating and Triggering a Campaign Now we have all the Pre-requisites to create a campaign To create a campaign, 1. Go to **Campaigns** from the left navigation bar under ‘Advanced’ section. 2. On the landing page of Campaigns, click on the ‘New Campaign’ CTA at the top right corner. It will open a popup as shown below. 3. Enter a name for your **Campaign** and select the notification event you want to fire using this campaign from the dropdown. 4. Once you have selected the event, you will see the channels linked to that event and also you will see a sample file structure which you need to upload. For ex - The selected notification event has only SMS channel, then you will see only SMS in the sample file structure.![](file:09d1be90-2f91-4855-8508-aa0b69ded91a) 5. Under ‘Create a campaign using’ select ‘CSV Upload’. 6. You can also download the sample CSV file by click ‘CSV for selected notification event’ . 7. The sample CSV file will have all the names of each channel configured in your template along with the placeholders as column names. 8. Once you have your CSV file ready, click ‘Upload CSV file’ or Drag and drop the CSV from your device. 9. Once the file is uploaded, you will see a few important details: 1. Number of records processed 2. Number of records ready to be imported 3. Number of records that are not valid (as per the checks in place). This could happen if there are any records without any destination and distinct Id etc. 4. Number of duplicate records that were found. 5. If there are any duplicates present in the csv uploaded and if you still want to include the duplicate data, then select the checkbox ‘Include duplicates in campaign’. ![](file:12cd6671-40b1-4bac-9d0d-2b98cf3ea4ac) 10. Click ‘Create Campaign’ to import the valid records from CSV. ### Configuring Campaign 1. The notification event is preselected based on the value selected. 2. **Map destinations & Placeholders -** In this step, you will need to configure the details needed for the event to be successfully triggered. This includes the mapping of the Channels and Placeholders. You can select each item’s corresponding data field from the uploaded CSV file by clicking on the drop-down and selecting one. In case you do not want to trigger a notification to a specific channel, you can remove it by deleting that row from this section. 3. Ensure all placeholders are properly mapped to your columns. For WhatsApp specifically, notifications will fail to deliver if any placeholder remains unmapped. 4. **Preview** - Preview allows you to visualize how the data from a CSV upload appears within the template, ensuring the uploaded data aligns with your expectations. You will see the preview as shown below. You can click ’<’ and ’>’ to see a preview based on the first 10 records from the uploaded CSV file. ![](file:a226d385-a315-446e-a669-b6d39468dfc3) ### How to test a campaign? Just before you send out a campaign to all your customers, running a test is always a good idea, since you will be able to preview the look and feel of your notifications before they go out. To do this, once you have set up your campaign, simply: 1. Scroll to the top of the campaign configuration page to find the **Run Test** button and click on it. 2. A new pop-up requesting the below information to run the test will come up: 1. **Send Using (Channel Details)**: Map the channels that are there in the notification event to run the test on. 2. **Map Placeholders**: Map the placeholders that are there in the template of the corresponding Notification event to successfully simulate the notification. 3. Once ready, click on run test to get the notification delivered to the corresponding test recipients. ### Save as Draft Once an event is configured with the details of the **Notification Event**, mapped Channels and Placeholders and scheduled time, this can now be saved to use or edit at a later time. Simply click on the **Save** at any point in time of configuring the campaign and this will be saved for later use! ### How to Fire or Schedule a campaign? Once you have done with all the configuration, you can click Schedule/Fire CTA. You can fire it in 2 ways. 1. **Now** - If you select Now and click ‘Fire’, the campaign will be fired immediately and your users will start getting notifications. ![](file:6b85b381-9b75-4c32-9046-1d4ebb9d81aa) 2. **Later** - If you select Later, you will be asked to select a date and time when you want to fire the campaign. ![](file:c52931ea-3615-4a31-a5e3-944eb5bd8504) You can select a date up to 30 days from the time of selecting the schedule. ### How to stop a campaign? If you want to pause a campaign after its fired, you can click the Stop Campaign and status of the campaign will show as Stopped. Please note that ‘Stop Campaign’ will be enabled only for CSV with more than 1000 records. ![](file:63cfdbfa-6074-45e5-b79f-778a29d32013) ## Viewing campaign logs & analytics Fyno’s **Campaign Analytics** allows you to visualise the performance as well as gain insights into your **Campaign** in the form of graphs and charts in one place, which helps improve the overall experience as well as outcomes pertaining to that notification event linked to that campaign. You can find your way to **Campaign Analytics** by: 1. Navigating to the **Campaign** page and clicking the “Bar Chart” icon corresponding to that particular campaign. OR 2. By clicking on a **Campaign** and clicking on the “View Analytics” CTA on the top right corner of the campaign. ### Overview The **Overview** section of the **Campaign Analytics** section provides an eagle-eye view of the campaign’s performance. On this card, you will see: - The number of times the notification event was fired - The number of notifications submitted via this notification event - The number of notifications delivered via this notification event. ### Channel Engagement **Channel Engagement** provides you with a detailed view of each channel used to send out notifications along with the outcomes of the notifications sent. Outcomes can be anything from: - **Submitted** - When a notification is successfully sent from Fyno’s platform - **Delivered** - When a notification gets successfully delivered to the destination (mobile number, email address, or device tokens like in the case of Push). - **Read/Open** - Read applies only to WhatsApp and In-App notifications. When any of these notifications are interacted with or opened, the provider returns a status as “Read” for all of these notifications. Whereas, Open applies only to email notifications. When an email is essentially “opened”, this will be tagged as “Open” and tracked on Fyno’s App. - **Clicked** - When a notification is clicked on, this will be tracked as a “Clicked” notification. This applies to In-App, Push, Emails with links, etc. ### Undelivered statuses are tracked when they are: - Invalid-Subscriber - Blacklist - Rejected - Bounce The count for each can be seen on hovering over the bar graphs. **You can highlight a single status to look at!**Simply click on the other statuses from the legend list at the bottom of the graph to un-select them! ### Delivery Status The delivery status graph shows you the delivery status by the channel that you have selected from the drop-down in the top right corner of the card. The list will populate the **Channels** based on usage and in chronological order of the count of each channel. You can toggle on or off the statuses you would like to see by clicking on the legends at the bottom of the graph. Let’s have a look at some of these statuses to understand it better. - **Sent** - All notifications that have left the Fyno App successfully towards the destination are marked as “Sent”. In scenarios where there is no delivery confirmation received from the provider, this status will remain as “Sent”. - **Delivered** - When a notification is delivered successfully to the Destination, then these messages are considered “Delivered” - **Error** - All notifications that fail to be triggered from the Fyno App due to some error (it may be any from an issue on a template to not choosing a provider for a channel), will be tagged as “Error” - **Failed** - When a notification is tagged as “Failed” this is most probably due to conditions that are mandatory from the provider that are not being met, due to which the notification execution has been tagged as “Failed” - **Bounce** - Bounce is a status that would be seen only in the case of an “Email” channel. This happens when 1. The email address is incorrect 2. The email address requires senders to be whitelisted in their domain to receive emails. 3. The email address’ mailbox is full and unable to receive any more notifications. ### Download Report You can download a report of a campaign by clicking ‘**Download Report**’ CTA. - You will receive an email with a downloadable link within a minute of raising a download report request. - You will also receive an InApp with the downloadable link for the campaign Report. The campaign report contains the following - **Request_ts** - When the campaign was fired. - **Request_id** - A unique id for each notification sent. - **Template** - Template name which is linked to the notification event fired via Campaign. - **Distinct_id** - A unique id for every user profile created in Fyno. If you are not using Fyno’s User Profile, this field will be blank. - **SMS_credits_use** - No of credits used for the SMS sent via this campaign. If SMS is not sent via the Campaign, this field won’t be there in the report. - **Email_credits_use** - No of credits used for the Email sent via this campaign. If Email is not sent via the Campaign, this field won’t be there in the report. - **<Channel>** - This will have the channel used in the template which is sent via Campaign. If your template has SMS, WhatsApp and message is sent to both the channels, then you will have 2 columns, SMS and WhatsApp. - **<Channel_submission_statuses>** - This will have the submission status of the channel used in the template which is sent via Campaign. If your template has SMS, WhatsApp and message is sent to both the channels, then you will have 2 columns, SMS_submission_status and WhatsApp_submission_status. - **<Channel_dlr_final_status>** - This will have the final status of the channel used in the template which is sent via Campaign. If your template has SMS, WhatsApp and message is sent to both the channels, then you will have 2 columns, SMS_dlr_final_status and WhatsApp_dlr_final_status. - **<Channel_dlr_statuses>** - This will have the all the statuses of the channel used in the template which is sent via Campaign. If your template has SMS, WhatsApp and message is sent to both the channels, then you will have 2 columns, SMS_dlr_statuses and WhatsApp_dlr_statuses.