Answers.Body: <p>The extension looks for specific MailChimp merge token names (FNAME, LNAME, and EMAIL). You can check it out in the function CRM_Mailchimp_Utils::updateContactDetails() if you want to see the guts of what it is doing. If your merge tokens are different, I think your options would be:</p>
  
  <ul>
  <li>update your tokens on the MC side </li>
  <li>hack the extension to hard-code your own token names instead of the default ones</li>
  <li>improve the extension by creating some kind of field mapping!</li>
  <li>create your own extension to override the functions that affect merge tokens</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-29T13:55:36.727Z
Answers.LastActivityDate: 2015-04-29T13:55:36.727Z
Answers.UserDisplayName: Nicholai
Body: <p>CiviCRM 4.4.14 (Drupal)</p>
  
  <p>I am trying to use the MailChimp integration extension but on importing a list from MailChimp, only the first name is imported. I've gone through all the settings but cannot find a way to get last name too.</p>
  
Tags: <import>
Title: MailChimp Integration imports First Name, but not Last Name
ThreadText: # MailChimp Integration imports First Name, but not Last Name
  
  (Asked by: username_0 on 2015-04-29)
  
  CiviCRM 4.4.14 (Drupal)
  
  I am trying to use the MailChimp integration extension but on importing a list from MailChimp, only the first name is imported. I've gone through all the settings but cannot find a way to get last name too.
  
  **Tags:** import
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-04-29. Score: 3
  
  The extension looks for specific MailChimp merge token names (FNAME, LNAME, and EMAIL). You can check it out in the function CRM\_Mailchimp\_Utils::updateContactDetails() if you want to see the guts of what it is doing. If your merge tokens are different, I think your options would be:
  
  * update your tokens on the MC side
  * hack the extension to hard-code your own token names instead of the default ones
  * improve the extension by creating some kind of field mapping!
  * create your own extension to override the functions that affect merge tokens
  
  
  ---
  
  