Not in your current configuration, as documented by your debug log.
For Pi-hole to block a given domain, that domain has to match an active entry from either an active blocklist or a manually created domain entry, and that entry and the requesting client have to share at least one group.
You'd typically create additional groups only if you'd want to filter some clients differently, along with defining clients for the group.
Note that for client-specific filtering to work, clients must talk to Pi-hole directly.
By default, all clients and blocklists are assigned to the default group, and the default blocklist is active, so no further action is required.
Now, you have manually added a single domain, but that domain is inactive:
id type enabled group_ids domain
----- ---- ------- ------------ -----------------------
2 1 0 0 ads-api.tiktok.com
As a result, that domain won't be blocked.
You'd have to enable that domain to have your Pi-hole filter it.
You have also created a custom group Add-on and added a bunch of blocklists to that group, including the ones that would match your domain.
However, there are no clients assigned to that group.
As a result, Pi-hole won't block anything from those Add-on lists for any client.
You'd either have to assign those lists to the default group, or create some clients and assign them to the Add-on group.