The detailed user guide of MindFire’s Work Flow Designer can be found HERE, and the user guide for the Direct Mail App is available HERE.
Please drag the Target Audience and the Direct Mail elements onto the canvas in the WFD, connect and configure them, as described in the HELP documentation mentioned above. Please also add the Microsite element that needs to be used for the traffic coming out of the QR code Direct mail. Please assign the correct domain to the microsite.
After the Microsite has been configured and the pages and the domain added to it, in the properties | settings section of the Direct Mail element, please add a new field called QRCodeString (or any other appropriate field name) by clicking on the green + sign at the bottom right.
Then right-click on the body of the new field and click on System Variables, as shown below
Click on Inbound Touchpoint in the menu that comes up now, as shown below.
Before we continue, we should discuss the source tracking and reporting, since that will impact the setup. Assuming we have both the QR code and printed PURL on the mailer, we will need to create two direct mail elements to track the traffic for both, as shown below. As shown below, we will assign the base domain to the direct mail element and a variant of the domain to the QR code inbound.
Please see below for the example of assigning domains to the outbound elements bringing in traffic to the Microsite.
The report by source (QR code vs Direct Mail Purl) can be shown by selecting the Report ID account-groupby-event-outbound in the Microsite Dashboard using the Dashboard Designer as shown below.
The resulting report will show something like the following example. If we have other outbound elements driving traffic to this microsite, we can add elements for those outbounds to this workflow, e.g. Email, social media etc.
Once we have the domain assigned, we will complete the configuration of the Inbound Touchpoint that we started in step 4 above, which will be used in generating the QR code string. We cannot finish this configuration of the QR code string without the proper assignment of the domains, since the domains are an integral part of the QR codes.
At this time, please click on the Inbound Touch Point menu option from step 4 above, and complete its configuration, as shown in the diagram below. Please provide a logical name to the Link (aka the Inbound Touch Point) which will show up in the report.
The configured value of the QR code string should look something like this:
##InboundTouchPoint Callback="1:3:2" PURL="true" PurlPosition="Prefix" CallbackName="QR Code"##
At this time, add a schedule to the QR code element, as shown below, to generate the QR code strings along with the export of the rest of the data.
An example of the output string generated for the QR code string will be:
johnsample.testdm.m.mdl.io/qr1?ocid=121&l=QR+Code
Where johnsample is the PURL, testdm.m.mdl.io/qr1 is the domain, and the two URL parameters ocid=121 and l=QR+Code are the source tracking parameters that will enable the reporting shown in the step 8 above.
Configuring the QR Code
MindFire’s QR code generator allows the users some control over the size, color and shape of the QR codes to be generated. Please see the screenshot below and the following text for available options.
Image size can be chosen as 100x100 (small), 200x200 (medium), 300x300 (large) or 500x500 (extra large).
Image format can be chosen as JPG or PNG
The image corners can be rounded
The image can be printed in color or grayscale
For color printing, users can select colors in the individual parts of the QR code, as illustrated above.
A small square image (max size 200x200) can be uploaded to be printed at the center of the QR code, as illustrated above.
Various QR Code Options
Let us now explore all the other options for creating QR codes. All the available options are highlighted in the screenshot below.
V-Card
When you select the V-Card option, the following model comes up where the specifics of the V-Card can be configured. The modal is pre-populated with default values. However, the users can change these default values, either by typing in a specific value (e.g. John Sample in the name fields).
A typical use case for the V-Card option could be to send a mailer from a mortgage company that has a QR code to scan to pull up the contact information of your loan office and save it on your phone. It is possible to have additional custom fields defined to carry the loan officer’s contact information, e.g. ##loanofficerfirstname##, ##loanofficer-firstname##, ##loanofficer-lastname##, ##loanofficer-email## and so on, and the user should be able to type those in before saving this QR code.
Google Map
The Google Map option opens up the modal shown below where the users can configure the address details to be shown on the map. The address can be a static address such as “123 Main Street”, “Los Angeles”, “CA”, “94332”. Alternatively, the users can use contact variables.
A typical use case associated with Google Maps can be mailers being sent by a Franchise, giving the location of the franchise location nearest to the person. Assuming fields like custom1 through custom5 are used to carry the address of the nearest franchise location, the above screenshot illustrates how the modal should be configured.
Phone Call
This provides the option to scan a QR code which will open up the phone application on the user's phone and pre-populate the phone number to be dialled. This is a great application for those that want a call back as a call to action.
When the phone option is selected, the system will prompt the user to provide a phone number. The user can either provide a static phone number or a variable such as ##phone##, as shown in the screenshot below.
In a typical use case, the user can provide a call-back phone number such as ##companyphone## along with a code such as a ##reservationid## that the system will automatically punch into an IVR system that answers the phone, allowing the respondent to announcing their identity to the IVR system. An example of how this can be achieved is by providing ##companyphone##,,,,##reservationid## in this modal.
SMS
This provides a call-back option to scan the QR code to respond with an SMS message. We should be able to open the default SMS app on the respondent’s phone, and optionally pre-populate it with a message.
A specific use case will be to respond back with a keyword. To achieve that the users should be able to type in ##mobile##?body:xxxxxx where xxxxxx is the pre-defined keyword that should be used as the callback response via the SMS message.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article