Campaigns problem

Still configurated my Mautic on my own server and have a problems with campaigns. I create a campaign form and a landing and then, I create a campaign process with campaign builder. When my leads feed the form, he should recevie an email but nothing happen.

I found this discussion : https://www.mautic.org/community/index.php/285-campaigns-won-t-send-emails/0

and set up all this CRON Jobs : https://www.mautic.org/getting-started/



Here are my CRON Jobs:

*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:leadlists:update --env=prod

*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:update --env=prod

*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:trigger --env=prod

0 6 * * * php /home/gradites/public_html/marketing/app/console mautic:email:process --env=prod



But email campaigns don’t seems to work for me. If I send test emails or a unique email to a lead, it’s work good but for campaigns nothing. What can it be?

Still configurated my Mautic on my own server and have a problems with campaigns. I create a campaign form and a landing and then, I create a campaign process with campaign builder. When my leads feed the form, he should recevie an email but nothing happen.
I found this discussion : https://www.mautic.org/community/index.php/285-campaigns-won-t-send-emails/0
and set up all this CRON Jobs : https://www.mautic.org/getting-started/

Here are my CRON Jobs:
*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:leadlists:update --env=prod
*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:update --env=prod
*/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:trigger --env=prod
0 6 * * * php /home/gradites/public_html/marketing/app/console mautic:email:process --env=prod

But email campaigns don’t seems to work for me. If I send test emails or a unique email to a lead, it’s work good but for campaigns nothing. What can it be?

Still on the same problem, all seems to work but It’s not sending email.

i check my CRON Job and on output, I have this, is it normal?

[code]
Mautic version 1.2.2 - app/prod

Usage:
command [options] [arguments]

Options:
–help (-h) Display this help message
–quiet (-q) Do not output any message
–verbose (-v|vv|vvv) Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
–version (-V) Display this application version
–ansi Force ANSI output
–no-ansi Disable ANSI output
–no-interaction (-n) Do not ask any interactive question
–shell (-s) Launch the shell.
–process-isolation Launch commands from shell as a separate process.
–env (-e) The Environment name. (default: “prod”)
–no-debug Switches off debug mode.

Available commands:
help Displays help for a command
list Lists commands
assets
assets:install Installs bundles web assets under a public web directory
bazinga
bazinga:oauth-server:clean Clean expired tokens
cache
cache:clear Clears the cache
cache:warmup Warms up an empty cache
config
config:debug Dumps the current configuration for an extension
config:dump-reference Dumps the default configuration for an extension
container
container:debug Displays current services for an application
debug
debug:swiftmailer Displays current mailers for an application
doctrine
doctrine:cache:clear Flush a given cache
doctrine:cache:clear-metadata Clears all metadata cache for an entity manager
doctrine:cache:clear-query Clears all query cache for an entity manager
doctrine:cache:clear-result Clears result cache for an entity manager
doctrine:cache:contains Check if a cache entry exists
doctrine:cache:delete Delete a cache entry
doctrine:cache:flush Flush a given cache
doctrine:cache:stats Get stats on a given cache provider
doctrine:database:create Creates the configured databases
doctrine:database:drop Drops the configured databases
doctrine:ensure-production-settings Verify that Doctrine is properly configured for a production environment.
doctrine:fixtures:load Load data fixtures to your database.
doctrine:generate:entities Generates entity classes and method stubs from your mapping information
doctrine:mapping:convert Convert mapping information between supported formats.
doctrine:mapping:import Imports mapping information from an existing database
doctrine:mapping:info
doctrine:migrations:diff Generate a migration by comparing your current database to your mapping information.
doctrine:migrations:execute Execute a single migration version up or down manually.
doctrine:migrations:generate Generate a blank migration class.
doctrine:migrations:latest Outputs the latest version number
doctrine:migrations:migrate Execute a migration to a specified version or the latest available version.
doctrine:migrations:status View the status of a set of migrations.
doctrine:migrations:version Manually add and delete migration versions from the version table.
doctrine:query:dql Executes arbitrary DQL directly from the command line.
doctrine:query:sql Executes arbitrary SQL directly from the command line.
doctrine:schema:create Executes (or dumps) the SQL needed to generate the database schema
doctrine:schema:drop Executes (or dumps) the SQL needed to drop the current database schema
doctrine:schema:update Executes (or dumps) the SQL needed to update the database schema to match the current mapping metadata.
doctrine:schema:validate Validate the mapping files.
fos
fos:oauth-server:clean Clean expired tokens
generate
generate:doctrine:entities Generates entity classes and method stubs from your mapping information
init
init:acl Mounts ACL tables in the database
mautic
mautic:assets:generate Combines and minifies asset files from each bundle into single production files
mautic:campaign:trigger Trigger timed events for published campaigns.
mautic:campaigns:rebuild Rebuild campaigns based on lead lists.
mautic:campaigns:trigger Trigger timed events for published campaigns.
mautic:campaigns:update Rebuild campaigns based on lead lists.
mautic:check:email Fetch and process monitored email.
mautic:check:mail Fetch and process monitored email.
mautic:email:process Processes SwiftMail’s mail queue
mautic:emails:process Processes SwiftMail’s mail queue
mautic:fetch:email Fetch and process monitored email.
mautic:fetch:mail Fetch and process monitored email.
mautic:install:data Installs Mautic with sample data
mautic:leadlists:rebuild Update leads in smart lists based on new lead data.
mautic:leadlists:update Update leads in smart lists based on new lead data.
mautic:lists:rebuild Update leads in smart lists based on new lead data.
mautic:lists:update Update leads in smart lists based on new lead data.
mautic:process:email Processes SwiftMail’s mail queue
mautic:process:emails Processes SwiftMail’s mail queue
mautic:process:webhooks Process queued webhook payloads
mautic:rebuild:campaigns Rebuild campaigns based on lead lists.
mautic:rebuild:leadlists Update leads in smart lists based on new lead data.
mautic:rebuild:lists Update leads in smart lists based on new lead data.
mautic:send:email Processes SwiftMail’s mail queue
mautic:send:emails Processes SwiftMail’s mail queue
mautic:transifex:pull Fetches translations for Mautic from Transifex
mautic:transifex:push Pushes Mautic translation resources to Transifex
mautic:translation:createconfig Create config.php files for translations
mautic:translation:debug Displays translation messages informations
mautic:trigger:campaign Trigger timed events for published campaigns.
mautic:trigger:campaigns Trigger timed events for published campaigns.
mautic:update:apply Updates the Mautic application
mautic:update:campaigns Rebuild campaigns based on lead lists.
mautic:update:find Fetches updates for Mautic
mautic:update:leadlists Update leads in smart lists based on new lead data.
mautic:update:lists Update leads in smart lists based on new lead data.
mautic:webhooks:process Process queued webhook payloads
oneup
oneup:uploader:clear-chunks Clear chunks according to the max-age you defined in your configuration.
oneup:uploader:clear-orphans Clear orphaned uploads according to the max-age you defined in your configuration.
orm
orm:convert:mapping Convert mapping information between supported formats.
router
router:debug Displays current routes for an application
router:dump-apache Dumps all routes as Apache rewrite rules
router:match Helps debug routes by simulating a path info match
server
server:run Runs PHP built-in web server
swiftmailer
swiftmailer:debug Displays current mailers for an application
swiftmailer:email:send Send simple email message
swiftmailer:spool:send Sends emails from the spool
translation
translation:debug Displays translation messages informations
translation:update Updates the translation file
yaml
yaml:lint Lints a file and outputs encountered errors
Set-Cookie: 869731cae0211075f1df32831b30c085=4999b8305bd9aabc59403b826fe50dea; path=/
Content-type: text/html; charset=UTF-8[/code]

thx

No, this is a list of available commands which will show up when you trigger just

Ok, it’s what I was thinking. Is there an error on my CRON?

/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:leadlists:update --env=prod
/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:update --env=prod
/2 * * * * php /home/gradites/public_html/marketing/app/console mautic:campaigns:trigger --env=prod
0 6 * * * php /home/gradites/public_html/marketing/app/console mautic:email:process --env=prod

What can of output should I have?

It seems fine. If the path to Mautic is correct. I cannot know that.

Every command has different output and it will tell you how the task went.

Path to Mautic should be good, I check again and was that. Is there any other option for what it’s not working? something I can missed in configuration? Something on the server, any special configuration? other things to do during installation?

Its looks like some CRON are working. if for example i add an “adjust lead points” during a campaign, it’s working. But for sending email, nothing. I can send one by one email to my lead but impossible to send email for campaigns.
My email are in “send immediatly” and don’t use queue and I connect to sendgrid to manage them.

If some campaign actions work, that mean the campaign cron work. If individual emails are sent, then it means that email is configured correctly. When we exclude those possible issues, the problem can be only in the campaign itself or in the testing.

Take a look at https://www.mautic.org/docs/pages/troubleshooting.html if that’s not the issue. If not, send here the screen shot of your campaign tree chart.

mmh, tracking pixel isn’t automaticaly include if we create a landing page? Right now, as I’m in test, I’m using a test landing page I create with the mautic builder (use the basic template “Nature”).
I follow the troubleshooting article. It’s look like the pixel wasnt include in may page. Then i include it. I can see it in “network tab” of my dev tool but the problem is, when I submit the form, i have a mistake on the same tab:
GET (canceled) /form/submit?formId=1:17

“Adjust leads point” is working but for example, “insert lead in a list” is not working and sending the email dont work too. I just create a fake campaign test.I let the screenshot here.

No, do not include the tracking pixel to a Mautic Landing Page. Mautic track its own pages automatically. The tracking pixel is only for 3rd party websites.

When I look at your campaign, I see these problems:

  1. When you crate a negative path from a decision (the orange one), you have to configure also the time delay when it should be considered as failed. If you don’t do that, it will be considered as failed immediately. The lead won’t even have a chance to open that email.
  2. When the lead source is the “Test submit form”, you already know that the leads in this campaign submitted that form. So delete the “Submits form” decision and send email directly.

Ok for the pixel. I delete it.

For the campaign, it was for testing. i guess leads point adjust because it was automaticaly considered as failed. But I never receive the first email, the one after “wait one minute”.
ok for submit form. It was i was thinking but wanting to try as I never receive email.
Also the “adjust lead list” is not workin. Should I always specify time delay for all actions?

No, time delay is required only for the negative paths. I’m getting out of ideas why the emails aren’t being send. Could it be that a lead can trigger every campaign only once? Take a look at the detail of your testing lead what actions can you see there.

ok, good to know for time delay. It’s strange. For one elad, 2 day ago, it’s appear “Triggered email1 event” and “Scheduled to execute at…” but I never received the email.
Also, cheking my CRON and the message in the output, I saw it’s possible to put sometimes the same command in singular and plural. (like mautic:campaigns:trigger and mautic:campaign:trigger). Can it be a reason? But I guess it should be in plural to execute all the campaigns right?

Singular and plural commands are just aliases. They do the same thing.