Demographics typically combine standard data elements such as age, gender, geographic location and job function with data elements specific to your organization. Together these elements create a donor profile that tells you who your donor is, and likely governs the tone and content of your messaging to that donor.Transactional data typically encompasses the recency, frequency and amount of donations, and also might include related data such as event registrations or product sales. This information provides a profile of what your donor gives, and likely governs the frequency and type of your gift requests.Engagement is about the point of entry, and the channel by which a constituent is most active. This is going to drive which channels you are using for those segments.
Contact Cadence, appropriate number and rhythm of communications based on the method of contact and the engagement levels of the constituent. Knowing your Segments means that you can better understand the communication policies your orgnaization should adopt and implement in the calendar
Donors who make two or more gifts in their first year are twice as likely to give the next year – this is Direct Mail, with email, we would expect the graph to take an even steeper turn between 30 and 60 days. There comes a point on this graph where if you haven’t gotten it within a time peroid, it isn’t worth the extra effort, because it isn’t a high ROI. Use personalized experience to encourage second gift within 100 days of their first gift
You can set this task to run on a daily or weekly basis.
First we’ll need check it the session variable is blank, if it is then we’ll set it based on a random number. Essentially, all the S55 tag and conditional is doing is saying “even” or “odd” – is the random number generated.
In our case A is show the splash page and B is show the donation form.
You can let the landing page set your session or you can override the session yourself with eithers_session_type=A or s_session_type=B
Mentioned during Users Group was using pgwrap=n for “view online” links for Email Stationary.
If you’re multi-center client be sure to use this in conjunction with s_AffiliateSecCatId.
If you’re multi-center client be sure to use this in conjunction with pw_id.
Usescid if your page needs folks to be added to a center, this is really only necessary if the page you’re displaying isn’t in the center you’re adding folks to or if there is an interaction that takes place that would make them a member of that center.
Steps to make this happen include pulling address and title information from the Content Type.Adding JS to spit out those addresses in a format for the GoogleMapsAPIInstall the GoogleMapsAPI
This is the “Take Home” portion of the slide deck….
Create a “printer friendly” link on your pagewrapper: <a href="[[S8]][[?[[S8]]::?::&amp;::?]]printer_friendly=1">Printer Friendly Version</a>
This is the “Take Home” portion of the slide deck….
Use the inspection tool to find the elements you want to change. Developer Tools will show you what styles are applied and where they are coming from and so can “s_jsfirebuglite=true”
To solve this across all pagewrappers, let’s make a reusable pagebuilder page called “reus_override_styles” and inside it we’ll start a stylesheet with any styles we want to be ours.Then add the pagebuilder as reusable to the very end of the Meta Head element when creating a pagewrapper (Step 2) – [[S51:reus_override_styles]]
When using our Developer Tools, we can find that the table row that contains the icons of the credit cards has it’s own ID – so we can apply a style to it to hide it just as easily as we could with javascript.
In this case, the radio button and amount are two different table cells inside the same table row. So we grab the closest thing with an ID and we’ll crawl the DOM through the parent nodes. Just one “.parentNode” would only get us to the table cell of the input, so we need to go up to another parent.