Answers.Body: <p>What I did was to keep big batches (bigger than the test groups) and allow to run several jobs, and then:</p>
  
  <pre><code>drupal_root=/var/www/drupal
  
  */5 * * * * www-data nice -n19 /usr/bin/drush -u 1 -r $drupal_root civicrm-api job.process_mailing auth=0 -y -l wemove
  */5 * * * * www-data nice -n19 /usr/bin/drush -u 1 -r $drupal_root civicrm-api job.process_mailing auth=0 -y -l wemove
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-21T16:00:37.960Z
Answers.Text: This is still not solving the problem 100%: if one of the processor, is busy processing another mailing, A and B will still be sent at different time
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-23T20:37:54.907Z
Answers.Text: Has this been resolved yet?
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-24T10:22:51.840Z
Answers.Text: Still not perfect. The ultimate plan is to move so the AB are part of the same mailing. Part of mosaico next version... and still looking for financial help to make it happen. Could you help?
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-24T16:08:09.220Z
Answers.Text: I'm not clear as to why AB testing functionality has to be bound up with mosaico. If there are details somewhere about what financial help is needed and what work needs to be done that would help if I'm approaching clients who may be interested in getting AB testing working properly.
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-26T14:20:18.017Z
Answers.Text: Basically, to be sure A and B are sent at the same time, it needs to be a single mailing, hence change of UI... and it's better to build on the top of mosaico for that ;) More information: https://wiki.civicrm.org/confluence/display/CRM/ABn+testing+v2
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-13T12:47:46.577Z
Answers.LastActivityDate: 2016-10-13T12:47:46.577Z
Answers.UserDisplayName: Xavier
Body: <p>When doing an AB test on two groups of 7k contacts, what seem to happen is that first the A group is sent in full, then the B group is processed.</p>
  
  <p>It obviously means that the second group is going to be sent later (in the latest experiment, 30 min later) than the first one, so obviously, it's a huge bias and it's hardly possible to compare the open or click rates, because A has such a head start.</p>
  
  <p>Is this possible to change the way the mails are sent to process the two groups as the same time? ie. change something on the cronjob?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-10-07T15:03:23.707Z
Comments.Text: We've also run in to this issue. Even when using multiple 'send' processes - CiviCRM still sends all the A batches and then starts on the B batches. This is perhaps something to raise in the issue queue? Since it sort of defeats the object of an A/B test.
Comments.UserDisplayName: John
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-22T11:55:27.353Z
Comments.Text: I did open an issue: https://issues.civicrm.org/jira/browse/CRM-20309
Comments.UserDisplayName: Djizeus
Tags: <abtesting>
Title: How to send A and B messages at the same time?
ThreadText: # How to send A and B messages at the same time?
  
  (Asked by: username_0 on 2016-01-19)
  
  When doing an AB test on two groups of 7k contacts, what seem to happen is that first the A group is sent in full, then the B group is processed.
  
  It obviously means that the second group is going to be sent later (in the latest experiment, 30 min later) than the first one, so obviously, it's a huge bias and it's hardly possible to compare the open or click rates, because A has such a head start.
  
  Is this possible to change the way the mails are sent to process the two groups as the same time? ie. change something on the cronjob?
  
  **Tags:** abtesting
  
  > **Comments:**
  > **username_1**: We've also run in to this issue. Even when using multiple 'send' processes - CiviCRM still sends all the A batches and then starts on the B batches. This is perhaps something to raise in the issue queue? Since it sort of defeats the object of an A/B test.  
  > **username_2**: I did open an issue: https://issues.civicrm.org/jira/browse/CRM-20309  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-10-13. Score: 3 | Accepted answer
  
  What I did was to keep big batches (bigger than the test groups) and allow to run several jobs, and then:
  
  ```
  drupal_root=/var/www/drupal
  
  */5 * * * * www-data nice -n19 /usr/bin/drush -u 1 -r $drupal_root civicrm-api job.process_mailing auth=0 -y -l wemove
  */5 * * * * www-data nice -n19 /usr/bin/drush -u 1 -r $drupal_root civicrm-api job.process_mailing auth=0 -y -l wemove
  
  ```
  
  > **Comments:**
  > **username_0**: This is still not solving the problem 100%: if one of the processor, is busy processing another mailing, A and B will still be sent at different time  
  > **username_3**: Has this been resolved yet?  
  > **username_0**: Still not perfect. The ultimate plan is to move so the AB are part of the same mailing. Part of mosaico next version... and still looking for financial help to make it happen. Could you help?  
  > **username_3**: I'm not clear as to why AB testing functionality has to be bound up with mosaico. If there are details somewhere about what financial help is needed and what work needs to be done that would help if I'm approaching clients who may be interested in getting AB testing working properly.  
  > **username_0**: Basically, to be sure A and B are sent at the same time, it needs to be a single mailing, hence change of UI... and it's better to build on the top of mosaico for that ;) More information: https://wiki.civicrm.org/confluence/display/CRM/ABn+testing+v2  
  
  ---
  
  