tag-manager
tag-manager copied to clipboard
matomo-org
Allow to Deactivate / Activate Tags instead of delete them
(feedback from customer)
Is it possible to perhaps have a on/off option for the tags?
Currently I can only turn a tag off by going to the tag in question -> advanced options -> and set a start date in the future to delay it
Furthermore, once a tag is paused I cannot see that it is paused - only when I again go to the tag -> advanced options.
Can we maybe add something next to the tags to indicate whether they are off/on? Something similar to what we have for versions when they are live/not live
A user comment:
"It would be interesting to have the possibility to make some tags inactive, to be able to send them to a "trash" and then recover them. For example, I need to do a test on several tags without deleting them, but I can't (unless I haven't seen the feature). Otherwise MTM is cool! Good job." Source: On-Premise
(User comment)
Feature: Like: No Choice: missingfeatures Feedback: Pause a tag so I can test other tags.. Source: On-Premise
(User comment)
...audit of our tags and I would like to know if it is possible to see a faster method or way to conveniently display tags that are currently enabled or disabled in production stage. At the moment, we would have to go through each tag in every container to see its state.
(User comment)
...audit of our tags and I would like to know if it is possible to see a faster method or way to conveniently display tags that are currently enabled or disabled in production stage. At the moment, we would have to go through each tag in every container to see its state.
if using startDate endDate, then a DB query would help to get the results faster
If using startDate endDate, then a DB query would help to get the results faster
For example, to search for tags active in April of 2023 a user could try
mysql> select * from matomo_tagmanager_tag where idsite=1 AND end_date<= 2023-04-01 AND start_date <= "2023-04-30 23:59:59" ;
In case it is convenient here is a description of the relevant table:
mysql> describe matomo_tagmanager_tag;
+--------------------+-----------------------+------+-----+-----------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------------+-----------------------+------+-----+-----------+----------------+
| idtag | bigint(20) unsigned | NO | PRI | NULL | auto_increment |
| idcontainerversion | bigint(20) unsigned | NO | | NULL | |
| idsite | int(11) unsigned | NO | MUL | NULL | |
| type | varchar(50) | NO | | NULL | |
| name | varchar(50) | NO | | NULL | |
| description | varchar(1000) | NO | | | |
| status | varchar(10) | NO | | NULL | |
| parameters | mediumtext | NO | | NULL | |
| fire_trigger_ids | text | NO | | NULL | |
| block_trigger_ids | text | NO | | NULL | |
| fire_limit | varchar(20) | NO | | unlimited | |
| priority | smallint(5) unsigned | NO | | NULL | |
| fire_delay | mediumint(8) unsigned | NO | | 0 | |
| start_date | datetime | YES | | NULL | |
| end_date | datetime | YES | | NULL | |
| created_date | datetime | NO | | NULL | |
| updated_date | datetime | NO | | NULL | |
| deleted_date | datetime | YES | | NULL | |
+--------------------+-----------------------+------+-----+-----------+----------------+
18 rows in set (0.00 sec)
This is a workaround.
It would still be nice to consider adding this feature.
User is trying to find source of an error and this feature, turning off a MTM tag would be VERY USEFUL to them in trying to isolate their problem.
This feature was requested today by a user.
Is there a way to selectively remove one off changes...?
This feature was requested today by a user.
Is there a way to selectively remove one off changes...?
@atom-box You can do this for now
- Export the container
- Remove the one of change
- Publish new container
- Import the container from the json exported in step1, now your draft state will contain the one of change and published state won't have that change