When you create an email in Infusionsoft builder it automatically attaches the contact information of the person you are sending it to.
This tutorial and accompanying video gives you the step-by-step on how to:
In the How to Find Table and Field Names in Infusionsoft video, 2014 Infusionsoft Partner of the Year Kim Snider provides a quick run-through of how Pocket Developer users can find all the necessary table and field names to make their lives that much easier.
In the How to Send Multiple Emails to Staff from Campaign Builder, 2014 Infusionsoft Partner of the Year, Kim Snider, quickly runs the audience through a demonstration of how they can use the Email Anyone, Anytime plug-in to send follow-up emails to the auxiliary contacts of a given Contact Record.
[wc_accordion collapse=”1″ leaveopen=”0″ layout=”box”]
[wc_accordion_section title=”What It Does”]
Prefetch is a feature built into our Advanced Merge Field Notation. Advanced Merge Field Notation is the way you tell Pocket Developer what field you want to work with. Prefetch allows you to burrow deep down into the tables to use a piece of data that is not easily retrieved using just the contact ID.
For those of you who are programmers, Prefetch is Pocket Developer’s version of a join. For those of you who aren’t, ignore that. Doesn’t matter.
Prefetch also allows you to save multiple pieces of data, coming from different places, into a single merge field. See the examples and demo video that follow to get a better idea of the power of prefetch.
[/wc_accordion_section]
[wc_accordion_section title=”Where I Can I Use It?”]
Prefetch is available anywhere Advanced Merge Field Notation is. All “Core” Pocket Developer plug-ins have Advanced Merge Field Notation and therefore can use Prefetch. Core plug-ins are the yellow ones in the Pocket Developer Store.
Core plug-ins include (at last count):
Check the Pocket Developer Plug-In Store for the most updated list and to see all 30+ Pocket Developer plug-ins.
[/wc_accordion_section]
[wc_accordion_section title=”How To Use It”]
To use Prefetch, include it as a parameter in an HTTP POST snippet that calls a core Pocket Developer plug-in.
prefetch[label]
To demonstrate some of the principles, consider the following example. Let’s assume that we would
like to get the quantity of a line item within an order, and then include it in the textToSave
parameter of the Any Text, Anywhere plug-in.
To achieve this result, we would define the following key/value pairs within an HTTP POST action within campaign builder:
contactId = ~Contact.Id~
prefetch[order_id] = Order.Id.Newest
prefetch[item_id] = OrderItem.Id.FilterBy(OrderId:{order_id}, ItemName:"Plan 1")
prefetch[item_qty] = OrderItem({item_id}).Qty
prefetch[notes] = Contact.ContactNotes
textToSave = User has ordered {item_qty} of item #{item_id} in order #{order_id}nn{notes}
saveTo = Contact.ContactNotes
This specific example would have the effect of prepending the “User has ordered …” line to
the contact’s ContactNote field.
prefetch[order_id] gets the ID of the newest order and stores it with a label of order_idprefetch[item_id] uses the previously stored order_id to get the ID of the item on that order called Plan 1 and stores it with a label of item_idprefetch[item_qty] uses the previously stored item_id to get the quantity ordered of that item and stores it with a label of item_qtyprefetch[notes] stores the contents of the big Contact Notes tab in the contact recordtextToSave prepends the string “User has ordered {item_qty} of item #{item_id} in order #{order_id}”. The codes “/n” create line breaks. Then the previous contents of the field are appended using {notes}.[/wc_accordion_section]
[wc_accordion_section title=”Demo Video”]
[/wc_accordion_section]
[wc_accordion_section title=”Frequently Asked Questions”]
Q. Where do I find all of the table and field names?
A.Infusionsoft has a complete reference for all the tables and fields you can use with Pocket Developer’s Advanced Merge Field Notation. Although the table names, in particular, may not be immediately obvious, the descriptions will help you find what information is stored in each table.
[/wc_accordion_section]
[/wc_accordion]
[wc_accordion collapse=”1″ leaveopen=”0″ layout=”box”]
[wc_accordion_section title=”Installing the Plug-In”]
You should have installed your Infusionsoft Pocket Developer plug-in using the instructions provided when you purchased the plug-in.
If, for any reason, you have not installed your Pocket Developer plug-in, follow these simple instructions, to learn how.
[/wc_accordion_section]
[wc_accordion_section title=”Configuring the HTTP Post Snippet”]
[wc_box color=”inverse” text_align=”left”]
NOTE: Everything in an HTTP POST is case sensitive. That includes the URL, the parameters on the left and the field names on the right. If caPitaLizaTion is wrong, your post will not work.
[/wc_box]
URL:
The URL, on your server, where the Pocket Developer script is stored. For example:
http://yourdomain.com/scripts/PocketDeveloper/Blocks/EmailAnyone/
to
templateId
from
cc
bcc
delete
[/wc_accordion_section]
[wc_accordion_section title=”Configuring the Email Template”]
Email Anyone Anytime uses email templates. Email templates can be found in the main Infusionsoft menu under Marketing.
As noted above, the from and to fields configured in the email template can be overridden by the plug-in, if desired.
When used with the Email Anyone Anytime plug-in, the subject line and email body can use our Advanced Merge Field Notation to merge information that is not available in standard Infusionsoft merge fields.
For example, you might merge the product purchased in the subject line or information from the contact’s company record in the body of the email.
NOTE: If you use Advanced Merge Field Notation in the subject or body copy, this email template cannot be used as a standard email template. Without the plug-in, the merge fields will appear as text in the email, without being merged. You might want to consider marking email templates that have Advanced Merge Field Notation so they aren’t used or changed accidentally.
[/wc_accordion_section]
[wc_accordion_section title=”Demo Video”]
[/wc_accordion_section]
[wc_accordion_section title=”Advanced Merge Field Notation”]
,
This Pocket Developer plug-in can use our Advanced Merge Field Notation anywhere a merge field is allowed. Advanced Merge Field Notation allows you to use merge fields from any table, e.g. Opportunity, Invoice, Company, Referral, Appointment, etc. It also allows you to Filter, Count, Max, Min, Compare, filter by IsEmpty and other advanced functionality.
For example, you may want to include the amount still due on an invoice in an email. Or, you may want to include the agreed upon services from an opportunity in an email. You can do this using Advanced Merge Field Notation.
See the Advanced Merge Field Notation documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Pre-Fetch”]
This Pocket Developer plug-in can build advanced data sets using our pre-fetch functionality. Pre-fetch allows you to find one piece of information, such as an ID, and pass it along to get to the exact piece of information you need.
For example, you may pre-fetch the Order Id before using it to get the line items on an order from the OrderItem table, to display in your email. This reduces the number of post snippets in a campaign and eliminates having to store a value in a field for the next step.
See the Pre-Fetch documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Contact Override”]
This Pocket Developer plug-in can merge information related to a contact other than the one going through the campaign, using our contact override functionality.
For example, you may want to create a notification email that includes the name and email address of the contact’s referrer as well as how many referrals that affiliate has made. You can do this using Override with our Advanced Merge Field Notation.
See the Contact Override documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Pro Tips”]
Use the Universal Delay Timer with Email Anyone Anytime, instead of standard Infusionsoft delay timers. You can configure the Universal Delay Timer so contacts are not “in” the campaign during the delays by not connecting the timer goal to the sequence before it.
[/wc_accordion_section]
[wc_accordion_section title=”Frequently Asked Questions”]
Q. Can’t I do the same thing with a legacy action set?
A. Email Anyone Anytime eliminates seven different roadblocks when sending email from Infusionsoft Campaign Builder. They are:
Legacy Action Sets only get you past one of these seven roadblocks.
And, of course, Infusionsoft has said legacy features, such as Action Sets, will go away at some point. We just don’t know when.
So why not future-proof your campaigns and turbo-charge your Infusionsoft emails at the same time?
[/wc_accordion_section]
[/wc_accordion]
Your product or service includes support for six months after purchase. You want to record the support expiration date for each product purchased and send the customer emails to get them to renew the support agreement prior to expiration.
Use the Pocket Developer Any Date, Any Format, Anywhere plug-in to add the term of your support agreement to the date of purchase. Put it in a custom field so you can merge it into emails and other communications.
[wc_box color=”success” text_align=”left”]
Exclusive Bonus – Read to the end to get the video of the private training I did for a client on this process with step-by-step set-up and in depth explanation of Pocket Developer superpowers.
[/wc_box]
You can set this up two ways. The easiest way is to put the end of support date in a custom field in the contact record. This way, it is easily accessible as a merge field and also can be seen easily by sales or support reps.
1. Install and configure Any Date, Any Format, Anywhere and Custom Delay Timer
2. In Campaign Builder, set up a sequence triggered by a Purchase Goal
3. Add two Any Date HTTP POST snippets, which add the support agreement term to today’s date
4. Add a Custom Delay Timer, to the end of the sequence, with a delay of 30 seconds. This gives the posts time to complete before sending the email with the details of your support agreement
5. Add a Field Timer, using your date field, from Step #3, to begin sending renewal notices prior to expiration.
The problem with the above is it burns two of your 100 custom fields in the contact record. It is also not a viable solution if the customer buys more than one product at different times.
You could, instead, use Any Date, Any Format, Anywhere, to put the expiration date in a custom date field in the order itself.
Then, use our Advanced Merge Field Notation, with the Universal Delay Timer plug-in, to run actions off the date in the order instead of from the Contact record.
When it comes time to use those dates for an email, you use Any Date to temporarily “stash” the date in the contact record. Once your email sequence is complete, use Any Text Anywhere to set your stash fields back to blank to be reused.
This method is a bit more work to set up. But, if custom fields are an issue, this technique can be applied in many different scenarios to save custom fields.
1. Install and configure Any Date Anywhere, Any Text Anywhere, Custom Delay Timer, and Universal Delay Timer
2. In Campaign Builder, set up a sequence triggered by a Purchase Goal
3. Add an Any Date HTTP POST snippet, which adds the support agreement term to today’s date and puts it in a custom date field in the order just placed.
4. If you want to send an email immediately, use Any Date to temporarily stash a pretty date in a contact field, as in step 3 in the Easy Setup. Then use Any Text Anywhere to set that field to blank, after the email has been sent.
5. Set up the Universal Delay Timer to restart the campaign a few weeks prior to the expiration date
6. Create an API Goal with the same callName as the previous step.
7. To send an email using the expiration date as a merge field, temporarily stash a pretty version of the expiration date in the contact record, as in Step #4 above. Set back to blank when email is complete.
8. Rinse and repeat as many times as needed for your renewal nag sequence to complete.
[wc_box color=”success” text_align=”left”]Exclusive Bonus – Get the video of the private training I did for a client on this process with step-by-step set-up and in depth explanation of Pocket Developer superpowers.
[/wc_box]
You can read more about Any Date, Any Format, Anywhere and see more examples of its usage in the QuickStart Guide.
Any Text Anywhere, Custom Delay Timer and Universal Delay Timer also have Quickstart Guides.
You can read more about Advanced Merge Field Notation and see more examples of its usage in the Learning Center.
To browse the entire catalog and purchase Pocket Developer plug-ins, visit our plug-in store.
[wc_box color=”go” text_align=”left”]
Don’t want to set this up yourself? Let one of our concierges do it for you. Just purchase all the necessary blocks. Then email concierge@theapiguys.com. We will have it all set up for you in a jif.
[/wc_box]
Q. Where do I find the table and field names for Advanced Merge Field Notation?
A. You can find the names of Infusionsoft tables and fields in the Infusionsoft Developer Resource Section under Table Documentation.
You can find the names of your custom fields by going to Infusionsoft Admin Settings -> Add Custom Field -> Record Type -> Show Database Name
[wc_accordion collapse=”1″ leaveopen=”0″ layout=”box”]
[wc_accordion_section title=”Installing the Plug-In”]
You should have installed your Infusionsoft Pocket Developer plug-in using the instructions provided when you purchased the plug-in.
If, for any reason, you have not installed your Pocket Developer plug-in, follow these simple instructions, to learn how.
[/wc_accordion_section]
[wc_accordion_section title=”Configuring the HTTP Post Snippet”]
[wc_box color=”inverse” text_align=”left”]
NOTE: Everything in an HTTP POST is case sensitive. That includes the URL, the parameters on the left and the field names on the right. If caPitaLizaTion is wrong, your post will not work.
[/wc_box]
https://tag-2025.local/scheduleCall or https://tag-2025.local/scheduleDelay
Take Note: this particular plug-in is not like our others, we host it. Since we manage the automated system which is continuously in-taking and processing calls, you should not specify your domain in this POST URL as you might in our other plug-ins.
appName
callName
date
1. A date or date & time which is structurally valid along common standards, such as “January 1, 2014 1:04 PM” or
“01/01/2014 01:04:33 PM” or “January 1st, 2014” or “01/01/2014” etc
2. The text “today” or “now” which will result in using the current date
3. A custom field that is holding a date or date/time value
Note: Only the date will be extracted from date/time values. Also, if you include a supported timezone code in your date value, please make sure it is using all capital letters (unless it’s an identifier), and that it appears as the last item in the date field. This will be overridden by any timezone values in the time or timezone parameters, if supplied. If no timezones are designated, assume that all dates are in Eastern Time as is the standard with Infusionsoft.
time
1. A time or date & time which is structurally valid along common standards, such as “January 1, 2014 1:04 PM” or “01/01/2014 01:04:33 PM”
2. The text “now” which will result in using the current time
3. A custom field that is holding a date or date/time value such as Anniversary, Birthday, or _MyCustomDate
Note: Only the time will be extracted from date/time values. Also, if you include a supported timezone code in your time value, please make sure it is using all capital letters (unless it’s an identifier), and that it appears as the last item in the time field. This will be overridden by any timezone values in the timezone parameter, if supplied. If no timezones are designated, assume that all times are in Eastern Time as is the standard with Infusionsoft.
adjustment
timezone
convertToTZ
saveKeyTo
groupName
override
[/wc_accordion_section]
[wc_accordion_section title=”Deleting a Scheduled Call”]
The deletion of a scheduled call is similar to the addition, or scheduling, of the initial call. Configuring the HTTP POST action is relatively more straight forward, but does require you read the scheduling instructions. If you haven’t read those yet, please see “Configuring the HTTP Post Snippet.”
The URL to specify within your POST action “POST URL” parameter is:
https://tag-2025.local/deleteCall or https://tag-2025.local/deleteDelay
There are two approaches to referencing the call or calls you’d like to delete.
[/wc_accordion_section]
[wc_accordion_section title=”Supported Timezone Codes”]
In the event you can’t find a timezone for your region within the list below, you may also use any of the timezone identifiers supplied at this PHP documentation page; some examples of these identifiers are America/New_York, Canada/Atlantic, etc.
| United States | ||
|---|---|---|
| Code | Timezone, State, or Region | Notes |
| ETUS | Eastern Time | No exclusions |
| CTUS | Central Time | No exclusions |
| MTUS | Mountain Time | Excluding Arizona |
| AZUS | Arizona (No DST) | No exclusions |
| PTUS | Pacific Time | No exclusions |
| ATUS | Alaska Time | No exclusions |
| HTUS | Hawaii/Aleutian Time | Excluding Honolulu |
| HONOUS | Honolulu | No exclusions |
| Australia | ||
|---|---|---|
| Code | Timezone, State, or Region | Notes |
| WTAU | Western Australia Time; Western Australia | Excluding Eucla |
| EUAU | Eucla, Australia Time; Western Australia | No exclusions |
| NCTAU | North Central Australia Time; Northern Territory | No exclusions |
| SCTAU | South Central Australia Time; South Australia | No exclusions |
| NETAU | North Eastern Australia Time; Queensland | No exclusions |
| SETAU | South Eastern Australia Time; New South Wales, Victoria, and Tasmania |
No exclusions |
| New Zealand | ||
|---|---|---|
| Code | Timezone, State, or Region | Notes |
| NZ | New Zealand Time | No exclusions |
| Europe | ||
|---|---|---|
| Code | Timezone, State, or Region | Notes |
| WTEU | Western European Time | Excluding Iceland |
| CTEU | Central European Time | No exclusions |
| ETEU | Eastern European Time | No exclusions |
| ICEEU | Iceland (No DST) | No exclusions |
| Canada | ||
|---|---|---|
| Code | Timezone, State, or Region | Notes |
| PTCA | Pacific Time; Yukon and British Columbia | No exclusions |
| MTCA | Mountain Time; part of Nunavut Northwest Territories, Alberta, Saskatchewan |
No exclusions |
| CTCA | Central Time; part of Nunavut, Manitoba, some of Ontario |
No exclusions |
| ETCA | Eastern Time; most of Ontario, Quebec, Baffin Island |
No exclusions |
| ATCA | Atlantic Time; Nova Scotia, New Brunswisk | No exclusions |
| NTCA | Newfoundland Time | No exclusions |
[/wc_accordion_section]
[wc_accordion_section title=”Demo Video”]
[/wc_accordion_section]
[wc_accordion_section title=”Advanced Merge Field Notation”]
This Pocket Developer plug-in can use our Advanced Merge Field Notation anywhere a merge field is allowed. Advanced Merge Field Notation allows you to use merge fields from any table, e.g. Opportunity, Invoice, Company, Referral, Appointment, etc. It also allows you to Filter, Count, Max, Min, Compare, filter by IsEmpty and other advanced functionality.
For example, you may want to delay based on the date an an opportunity is expected to close or an appointment date and time. You can do this using Advanced Merge Field Notation.
See the Advanced Merge Field Notation documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Pre-Fetch”]
This Pocket Developer plug-in can build advanced data sets using our pre-fetch functionality. Pre-fetch allows you to find one piece of information, such as an ID, and pass it along to get to the exact piece of information you need.
For example, you may pre-fetch the Id of an opportunity owner before using it to get the date of the next appointment with the opportunity owner from the ContactAction table, to send a reminder email. This reduces the number of post snippets in a campaign and eliminates having to store a value in a field for the next step.
See the Pre-Fetch documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Contact Override”]
This Pocket Developer plug-in can merge information related to a contact other than the one going through the campaign, using our contact override functionality.
Imagine you do marriage counseling, for example. You may want to delay a reminder email, to a spouse, based on the appointment date in the record of the other spouse. You can do this, using Contact Override, with our Advanced Merge Field Notation.
See the Contact Override documentation for more details.
[/wc_accordion_section]
[wc_accordion_section title=”Pro Tips”]
[/wc_accordion_section]
[wc_accordion_section title=”Frequently Asked Questions”]
Q. Can’t I do the same thing with an Infusionsoft field timer?
A. Field timer only gives you access to date fields in the Infusionsoft contact record. Universal Delay Timer allows you to use any field, in any table (e.g. Opportunity, Invoice, Company, Referral, Appointment, etc.) that represents a valid date.
Infusionsoft’s field timer requires the date to be contained in a date field. Universal Delay Timer can take a date in any format, including text (e.g next Thursday or September 13)
Infusionsoft’s field timer also does not allow the time to be set dynamically from a field. It is a drop-down in the timer. With Universal Delay Timer, the time field can also be any field, in any table, representing a time.
[/wc_accordion_section]
[/wc_accordion]
[wc_accordion collapse=”1″ leaveopen=”0″ layout=”box”]
[wc_accordion_section title=”Installing the Plug-In”]
Note: You should have installed your Infusionsoft Pocket Developer plug-in using the instructions provided, if for any reason you have not installed your Pocket Developer plug-in click here to learn how.
[/wc_accordion_section]
[wc_accordion_section title=”Configuring the HTTP Post Snippet”]
[wc_box color=”inverse” text_align=”left”]
NOTE: Everything in an HTTP POST is case sensitive. That includes the URL, the parameters on the left and the field names on the right. If caPitaLizaTion is wrong, your post will not work.
[/wc_box]
URL:
The URL, on your server, where the Pocket Developer script is stored. For example:
http://yourdomain.com/scripts/PocketDeveloper/Blocks/TagsFly/tagsfly.php
Required Name Value Pairs:
contactId
Optional Name Value/Pairs:
default
request
override
[/wc_accordion_section]
[wc_accordion_section title=”Demo Video”]
[/wc_accordion_section]
[wc_accordion_section title=”Pro Tips”]
[/wc_accordion_section]
[wc_accordion_section title=”Frequently Asked Questions”]
[/wc_accordion_section]
[/wc_accordion]
