eloqua page- email field merge
What is difference between First Name used for Forms and First Name used for Email Only in Oracle Eloqua??
These are default field merges provided by Eloqua. The "for Forms" has no default value if blank, so if the user matches an existing cookie but does not currently have a First Name on their corresponding contact record, nothing will prepopulate on the form. You wouldn't want a default value to potentially be set to their contact record if they submit the form without changing the value. Conversely, the "for Email Only" has a default value set, since in most emails you might not have a first name, but you rather have "Hi Loyal ACME Customer," than "Hi ,".
Related
I would like to send several dems to an e-mail address with different customizations based on the information present in a Custom Object.
Es.
Email Address = xxx#x.com
Custom Object:
3 records with different information to be printed in the email to be sent.
Is there a way to ensure that multiple emails can be sent to an email address simultaneously with different customizations?
Is there a workaround for last created field merge etc?
Yes.
Create a dynamic for each demo, create decision steps on the canvas which check to see if the field in the cdo has the correct value, if not pass it to the next decision step.. if yes, pass it to the email which passes to the next decision step, like this:
Multi step campaign canvas example
I'm exploring Twilio Autopilot. I trained a task with an annotated field to collect the user's first name. However it seems like every time I submit a request to this task, the new first name just gets added to an array. E.g. I have the sample set up as something like:
Hi there, my name is {first_name}.
If I submit it 3 times like this:
Hi there, my name is Frank.
Hi there, my name is Bill.
Hi there, my name is Jim.
By the third time, it is submitting an array of [Frank,Bill,Jim] for the Field_first_name_Value request parameter.
Is there any way to configure it so we overwrite the value every time we submit the field?
Twilio developer evangelist here.
At the moment, there is no way to configure it so the value is overwritten each time the field is submitted. I've passed this on to the product team as a feature request!
In the following URL, that unsubscribes a user from a list:
http://xxxxx.us2.list-manage.com/unsubscribe?
u=87f537bccxx35e53a1890e0d9&
id=40dcxx6cd6&
e=c4aaxx1dd6&
c=9a6xx11963
What does each parameter do?
Today I had to learn what each nondescript parameter means so that I could generate URLs for each email I send through Mandrill. It wasn't that easy to discover their meaning, but here are the one's I've come up with and how I found out what they are.
http://xxxxx.us2.list-manage.com/unsubscribe?
u=87f537bccxx35e53a1890e0d9&
id=40dcxx6cd6&
e=c4aaxx1dd6&
c=9a6xx11963
URL format:
Protocol can be http or https.
Your username comes next
In the example, us2 is the MailChimp datacenter where your account resides. That's different for each account. (https://apidocs.mailchimp.com/api/2.0/) It's good practice to specify a DC even though the documentation says that it isn't required. Specifying it will cut down on unnecessary latency.
list-manage[n].com can work with or without the number at the end of the domain, or it can have a 1 or a 2. Changing that doesn't appear to matter, but I think it has something to do with their load balancing.
/unsubscribe can also be /subscribe or /profile (The latter appears to be dependent on the "e" parameter. (See below) When you don't specify it, it states, "List member profiles cannot be updated from test campaigns or archive pages" and if you specify an invalid value, you get an error page.
u Is a unique identifier for your account. Every list on your account uses it. (See http://kb.mailchimp.com/lists/signup-forms/find-the-unsubscribe-link-for-your-list for how you can view the various URLs for your account.)
id is your list ID
e is the euid as documented on https://apidocs.mailchimp.com/api/2.0/lists/subscribe.php
c I haven't seen this one yet, but my guess is that it's the campaign ID.
Also, when you wish to prefill subscribe and unsubscribe forms, you can use the following GET params.
EMAIL Allows you to enter the subscriber's email
MERGE1 Allows you to enter the subscriber's first name
MERGE2 Allows you to enter the subscriber's last name
I've had experience with making custom validation in Zend Framework 2 (using version 2.0.5 at present). I'm interested in creating a change password section in an "edit profile" form. What I want to be able to do, is have 3 fields:
Current Password,
New Password,
Confirm New Password.
Then I want to validate as follows:
If a new password is set, current password must also be set (and authenticated), and confirm new password should match new password.
If a current password is set, the new password and confirm new password must also be required.
If none are set, allow the edit of the rest of the profile, so continue validation.
I think you can get the gist of what I'm after, I'm looking for a reusable way to do this using Zend Framework 2. Ideally, creating a custom validator so that the forms can be reused, thought I suspect a factory approach may be better. Anything so I don't have to check it in the controller/service layer and repeat myself wherever I want to use this.
Kind Regards,
ise
You could add a custom filter, but I think this could also be done using validation groups and separately validate groups of inputs.
you could add the password fields to a separate group and only validate that group if the main password is not empty.
http://framework.zend.com/manual/2.0/en/modules/zend.input-filter.intro.html
http://framework.zend.com/manual/2.0/en/modules/zend.form.collections.html#validation-groups-for-fieldsets-and-collection
We currently have a Jira instance and I have had another odd request to sort the posts by the number of customers affected. Is this at all possible or will this require some custom work on my part?
Simplest is to add a customer impact number to your configuration (a custom field of type number) and bump it each time a new customer is added to the company name field.
You might even add a simple javascript which automatically sets the field if the company name field is modified ...